WordPress Charset Encoding Problem After Upgrading to Version 2.2
WordPress blogs that upgraded to Wordpress version 2.2 may encounter strange character set (charset) encoding problem where several characters especially apostrophes (’), quotation marks (”), and hyphens or dashes (—) are displayed as strange characters such as ’ or simply as question marks (?) when the posts are output to web pages. As you have probably suspected, the issue is caused by character encoding method used by WordPress 2.2 which supports setting of database collation and character set in WordPress config file.
The error happens because up to and including WordPress ver 2.1.3, almost all WordPress databases were created using the latin1 character set and the latin1_swedish_ci collation. Beginning WordPress v2.2, WordPress allows the user to define both the database character set and the collation in wp-config.php file, using DB_CHARSET and DB_COLLATE values. With these values set to another encoding, WordPress assumes that the databases are indeed using the charset and collation too, where it’s not the case for existing WordPress installation. So if you’re upgrading WordPress to 2.2 using the default wp-config.php, or have manually modified the file to include the new variables, or upgrading by using Fantastico which automatically update the wp-config.php file to include these two definitions which values set as Unicode UTF-8 by default, you will need to remove these definitions to solve the character encoding error.
Open and edit your WordPress wp-config.php file. Then locate the following two lines:
define(’DB_CHARSET’, ‘utf8′);
define(’DB_COLLATE’, ”);
You can simply delete these 2 lines away, or just remove the utf8 from the first line to make them looks like this:
define(’DB_CHARSET’, ”);
define(’DB_COLLATE’, ”);
With no charset and collation values set, WordPress will fall back to the old default, latin1 which matched the databases.
A possible better solution is convert the Wordpress database to UTF8 Unicode.
Related Articles
- How to Convert Character Set and Collation of WordPress Database
- Automatically Update WordPress to Latest Version with Automatic Upgrade Plugin (WPAU)
- Download Previous or Old Version of WordPress
- Latest Version of WordPress 2.3.1 Released
- WordPress 2.2 Released for Free Download
- How to Customize, Modify or Change WordPress Database Connection Error Page
- Disable and Turn Off Post Revisions Tracking in WordPress 2.6 or Above
- Paginating or Split WordPress Post or Page with NextPage in WordPress Not Working
- How to Change the Frequency or Interval WordPress Auto Saves An Editing Post or Page
- How to Move WordPress Blog to New Domain or Location
Entries (RSS)
July 4th, 2009 05:18
[...] Update: Chinese and Swedish alike should be displayed properly now. The problem arises when converting to new versions of WorpPress, but by changing a few parameters, it’s possible to let WordPress revert to the old way of handling charactersets. The solution to the problem can be found here. [...]
May 3rd, 2009 11:20
I solved following these steps:
http://www.levysoft.it/archivio/2007/07/06/risolvere-il-problema-della-visualizzazione-errata-dei-caratteri-accentati-su-wordpress-cambiando-il-charset-da-iso-8859-a-utf-8/
March 29th, 2009 05:14
Hello!
Very Interesting post! Thank you for such interesting resource!
PS: Sorry for my bad english, I’v just started to learn this language
See you!
Your, Raiul Baztepo
January 31st, 2009 02:33
Thank you a lot! It worked out perfectly. Now, I have to convert everything to UTF8.
December 23rd, 2008 12:49
[...] WordPress Charset Encoding Problem After Upgrading to Version 2.2 اقرأ المزيد عن …أهلا 2.5، ومرة أخرى مشكلة الترميز بحمدالله تم الانتقال إلى النسخة الحديثة 2.5 من ووردبريس، وكل…ما الجديد! تم اصدار نسخة جديدة من برنامج ووردبريس، وكما ذكر في…WYSI-Wordpress محرر نصوص متقدم Wysi-Wordpress محرر تنسيق المدونات لمن يريد اختيارات أكثر و حرية… [...]
October 17th, 2008 13:15
Thank you for this post!
September 16th, 2008 10:05
[...] caused due to the encoding and collation, however after following the recommendations of sites like http://www.mydigitallife.info/2007/0…to-version-22/ I was still unable to get rid of the huge amount of garbled characters. Ultimately, I spent some [...]
September 6th, 2008 19:50
Thanks so much — you saved me hours of hair pulling!
August 24th, 2008 11:20
Thanks! Saved me a lot of time.
August 23rd, 2008 05:24
thanks
June 18th, 2008 08:42
Isn’t UTF8 much better? Why would you limit yourself to Latin1 just because it used to be the default?
June 6th, 2008 20:56
Just wanted to say: this had afflicted me for months. Never found a workable solution. Stumbled on your site today and it worked perfectly. Thanks so much!
February 19th, 2008 05:04
Hi, thanks for doing this. it’s the only thing I’ve found. I remove the utf8 and a lot of my posts still have the question marks. any ideas what I may need to do?
February 17th, 2008 03:44
thanks for the help, it worked out for me
January 5th, 2008 06:55
Thx a lot!
You saved me hours!