Project

General

Profile

Actions
Copy link

Defect #14578

closed

After an update from 1.4.3 to 2.3.2 german umlauts in custom fields are broken

Added by ITF-EDV Admin over 11 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Custom fields
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:
2.3.2

Description

The update of all components went fine but all german umlauts only in the customs fields (we added some lists) were broken.
The umlauts in the GUI are ok.

If i add another custom field after the update the umlauts in this new field are fine. Even if i edit our lists the edited umlauts are ok. But i don't want to edit a few hundred entries manually and brake database relationships eventually.

The database is (and was before the update) in utf8 format and the umlauts are correctly stored in the DB.

Environment:
Redmine version 2.3.2.stable
Ruby version 2.0.0-p247 (2013-06-27) [x86_64-linux]
Rails version 3.2.13
Environment production
Database adapter Mysql2

Files

Download all files
broken_umlauts.jpg (54.4 KB) broken_umlauts.jpg ITF-EDV Admin, 2013-07-30 17:23
screenshot_with_1_4_3_all_umlaut_ok.png (70.6 KB) screenshot_with_1_4_3_all_umlaut_ok.png ITF-EDV Admin, 2013-07-31 16:32
screenshot_with_2_3_2_umlauts_are_wrong.png (71.9 KB) screenshot_with_2_3_2_umlauts_are_wrong.png ITF-EDV Admin, 2013-07-31 16:32
Actions
Copy link

Also available in: Atom PDF