New to the community? Start here

UTF error after migration

I did a package migration using shipper and all of the “Umlaute” in the German language like ä, ö, ü are wrong and there are strange characters on the destination site.

Mon, 27 Jan 2020 19:45:48
More Shipper Pro discussions
Shipper Pro
  • Adam
    • Support Gorilla

    Hi Andreas Ursprunger

    I hope you’re well today and thank you for contacting us!

    Just to make sure: you have migrated from “qui…og.wpmudev.host” to “ueb…en.qui..og.com”, correct?

    I’m assuming that on the new host you have some sort of direct access to the database (.e.g via cPanel/phpMyAdmin) so I’d like to ask you to check something there:

    on that new site, could you please access the database and in phpMyAdmin check

    – what’s the “Server connection collation” option currently set to (you’ll see it on the main screen of “phpMyAdmin” – just click on the “home” icon after logging in)?

    [attachments are only viewable by logged-in members]

    – then select your database and in “Structure” tab look at the “Collation” column – what does it say? if there are different settings for different tables – what are they?

    [attachments are only viewable by logged-in members]

    Let me know, please.

    Kind regards,
    Adam

  • Andreas Ursprunger
    • Flash Drive

    Hi Adam,

    Many thanks for your Input! Now i did it by myself!! Under Operations i changed everything (also columsn) to utf8mb4_unicode_ci and now everything is working. Although it is strange, because
    on the phpadmin page under operations and Collation there was the following “setting”: latin1_swedish_ci
    And that was not the “original” setting bevor making the package via Shipper/package migration.
    So i think that this is a bug in the shipper plugin. Maybe you will check that!!

    Many thanks,
    Andi

  • Adam
    • Support Gorilla

    Hi Andreas Ursprunger

    Thank you for response and I’m sorry for the delay on my end.

    I’m glad to hear that you managed to solve that!

    I’m wondering though why those settings in the new database were different than those on original one. The package migration should carry over character set/collation “as they are” from the original database so that might, indeed, need further investigation on our end.

    Just one more question though, to make sure: it was package migration, right? So, before running the install script on the target site – did you create a completely fresh, empty database for it?

    Best regards,
    Adam