Moving a WordPress database to "all UTF8" can be problematic. Without taking note of the specific scenario, you might find yourself struggling with messed up encoding (on not-ascii chars). If you find yourself manually replacing messed up chars in a database, stop! You should never need to do this. Only in the worst cases of "split brain encoding" might you need to do something like that.
When moving a WordPress database to a new charset, it's not uncommon for there to be a mixture of latin
and utf8
in different settings. This is because WordPress' default encoding used to be latin1
a long time ago. To confuse things furthere, there can also be a mismatch between WordPress' understanding of the encoding for the database, and MySQL's.
You must find the value of DB_CHARSET in WordPress. This is typically in the wp-config.php
, however it might not be. WordPress has a default value, which can vary depending if you are using a DB drop-in pl