Phil7789 Posted January 28, 2016 Share Posted January 28, 2016 Hey guys, I installed a demo board to test and upgrade from 3.x to 4.x of the suites version. Although I've always used utf8 encoding the script told me that not every table was set correct, so it needed to be fixed. It was changed from utf8_general_ci to utf8_unicode_ci. My problem now is: before the upgrade the german 'Umlaute' worked perfectly (ö, ä, ü, ß). After the upgrade I'm getting cryptical symbols. Editing those lines and setting e.g. ö again fixes this. It is then displayed as ö. Now my question is: Is this intended or is there any quick solution how to change those bugs throughout the suite? I've seen a script from adminarea.de but before I am going to register and try this script, I wanted to know if this is normal or if there is any other solution? Thanks in advance Phil Link to comment Share on other sites More sharing options...
Eidorian Posted February 21, 2016 Share Posted February 21, 2016 I have the same problem. Regards. Link to comment Share on other sites More sharing options...
MataVirgenes Posted February 23, 2016 Share Posted February 23, 2016 i resolved with this: ALTER TABLE tablename CONVERT TO CHARACTER SET utf8 COLLATE utf8_unicode_ci; Link to comment Share on other sites More sharing options...
hmikko Posted February 25, 2016 Share Posted February 25, 2016 I had the same problem when I first converted from 3.4.8 to 4.0.0. My database was damaged although pages show up correctly in 3.4.8 (ü, õ, ö, ä). In 4.0.0 they were like õ for õ, ü for ü, ä for ä and so on. After I ran multiple (beta) conversions I eventually got everything working. Somewhere should be my bug reports as well. Did ju ran IPS UTF8 Database Converter? Link to comment Share on other sites More sharing options...
TheSonic Posted February 28, 2016 Share Posted February 28, 2016 We had users with such problems, especially with older databases converted from other scripts. So, if you are sure your databasesttings are setup fine, you may try running this script: http://www.adminarena.de/files/file/8-charconvzip/ Link to comment Share on other sites More sharing options...
opentype Posted February 28, 2016 Share Posted February 28, 2016 2 minutes ago, TheSonic said: We had users with such problems, especially with older databases converted from other scripts. So, if you are sure your databasesttings are setup fine, you may try running this script: http://www.adminarena.de/files/file/8-charconvzip/ I wouldn’t recommend using that. That problem is caused by a general character encoding mismatch. Running a script that fixes a few selected characters will very likely not catch all affected characters. The whole character set needs to be converted instead. Link to comment Share on other sites More sharing options...
TheSonic Posted February 28, 2016 Share Posted February 28, 2016 I don't force people to use it, but for some people it was a last ressort and their sites are fine until now But you're do it on your own risk.... Link to comment Share on other sites More sharing options...
.thumb.png.72c24494603afd7a572d55d4a71e4af2.png)
Recommended Posts
Archived
This topic is now archived and is closed to further replies.