Title: Encoding issue
Last modified: September 1, 2022

---

# Encoding issue

 *  Resolved [charlene](https://wordpress.org/support/users/pixibuex/)
 * (@pixibuex)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/encoding-issue-9/)
 * I’m having an encoding issue: [https://i.imgur.com/xtaT9O3.png](https://i.imgur.com/xtaT9O3.png)
   When I check the sql file inside the exported .wprime file (by renaming it as.
   tar and unzipping), I see the characters all wrong. So the database encoding 
   is not correct in the export file. Any suggestions to make the encoding work 
   properly for Turkish content?

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Author [Codexonics](https://wordpress.org/support/users/codexonics/)
 * (@codexonics)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/encoding-issue-9/#post-15971043)
 * 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](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](https://codexonics.com/contact/).
   Once we have all the info – please give us time to analyze and debug the issue.
   Our support timezone is GMT + 8.
 * Thanks again!
 *  Thread Starter [charlene](https://wordpress.org/support/users/pixibuex/)
 * (@pixibuex)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/encoding-issue-9/#post-15971123)
 * Thank you for getting back to me. Just sent the requested files through the contact
   form.
 *  Plugin Author [Codexonics](https://wordpress.org/support/users/codexonics/)
 * (@codexonics)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/encoding-issue-9/#post-15971305)
 * 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
 *  Thread Starter [charlene](https://wordpress.org/support/users/pixibuex/)
 * (@pixibuex)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/encoding-issue-9/#post-15972618)
 * It worked! Thank you for your help.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Encoding issue’ is closed to new replies.

 * ![](https://ps.w.org/prime-mover/assets/icon-256x256.png?rev=2114612)
 * [Prime Mover - Migrate WordPress Website & Backups](https://wordpress.org/plugins/prime-mover/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/prime-mover/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/prime-mover/)
 * [Active Topics](https://wordpress.org/support/plugin/prime-mover/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/prime-mover/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/prime-mover/reviews/)

## Tags

 * [encoding](https://wordpress.org/support/topic-tag/encoding/)
 * [turkish](https://wordpress.org/support/topic-tag/turkish/)
 * [utf-8](https://wordpress.org/support/topic-tag/utf-8/)

 * 4 replies
 * 2 participants
 * Last reply from: [charlene](https://wordpress.org/support/users/pixibuex/)
 * Last activity: [3 years, 7 months ago](https://wordpress.org/support/topic/encoding-issue-9/#post-15972618)
 * Status: resolved