Encoding issue

Hello Charlene,

Thank you for using Prime Mover! Sorry to hear you have an encoding issue. We would like to reproduce this issue in our end. Can you please provide us the following?

• The link to download the WPRIME package. You can upload this package to Google Drive/DropBox and share us the link to download.
• Login to your source site (where the package is created) and go to Prime Mover -> Advanced -> Export site info -> and click “Export site info” button. This will download the site info log of your source site. Rename the log file to ‘sourcesite.log’ – so that we will know it’s from the source site.
• Send us some screenshots as to how these characters would look like (expected result) at the source site. So we will know the equivalent correct result of this screenshot: https://i.imgur.com/xtaT9O3.png
• Login to your target site (where you want the package to be restored) and go to Prime Mover -> Advanced -> Export site info -> and click “Export site info” button. This will download the site info log of your source site. Rename the log file to ‘targetsite.log’ – so that we will know it’s from the target site.
• [optional] If you can provide a correct MySQLdump .sql file with the correctly encoded Turkish characters (not generated by Prime Mover but using another tool in your source site that is correct) – please include so we will know how these characters are encoded at the source site

Please send us all the requested info in our contact form. Once we have all the info – please give us time to analyze and debug the issue. Our support timezone is GMT + 8.

Thanks again!

Thank you for getting back to me. Just sent the requested files through the contact form.

Hi Charlene,

Thanks for the details. We’ve checked the source site DB charset and collation and it looks different from the target site.

Can you please set these following constants in your target site wp-config.php? Make sure your target site DB_CHARSET and DB_COLLATE values are as follows:

define( 'DB_CHARSET', 'latin1' );
define( 'DB_COLLATE', 'latin1_swedish_ci' );

This makes it the same with the one used in your source site. In our own tests, if we use the above DB_CHARSET and DB_COLLATE values in our source site and then we migrate it to a target site with different charset values (e.g. utf8) – it will cause encoding issues and characters won’t display correctly.

However if we change the DB_CHARSET and DB_COLLATE values of the target site with the same values as the source site (for charset encoding compatibility) – the encoding will look correct.

This should fix the issue. If it works – please mark this ticket as resolved. If not – please let us know so we will check further. Thank you!

Cheers,
Emerson

It worked! Thank you for your help.