| Summary | convert_prefs_to_sql.php and german Umlauts |
| Queue | Ingo |
| Queue Version | 1.2.4 |
| Type | Bug |
| State | Not A Bug |
| Priority | 2. Medium |
| Owners | |
| Requester | mg (at) mdlink (dot) de |
| Created | 06/07/2010 (5514 days ago) |
| Due | 06/03/2010 (5518 days ago) |
| Updated | 06/15/2010 (5506 days ago) |
| Assigned | |
| Resolved | 06/15/2010 (5506 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
We found the cause. There was a problem with the character set in
mysql. Therefore, some german umlauts were interpreted as y.
So thats not a problem with the ingo convert script.
Regards,
Mario
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ convert_prefs_to_sql.php and german Umlauts
Due ⇒ 06/03/2010
Queue ⇒ Ingo
Milestone ⇒
Patch ⇒ No
We did an upgrade from an old Ingo (v1.0) to the current stable
version (v1.2.4).
We used the script convert_prefs_to_sql.php and no errors were
detected. So everything seemed to work fine.
But now we determine an error. The old prefs-records with german
Umlauts didn't convert to the new db tables. So many filters are lost.
The script ignores the complete record if there is a german Umlaut in
it.
We suppose that this is a bug in the script.
Can anyone confirm this?
Regards,
Mario