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.
Share and contribute or get technical support and help at My Digital Life Forums.
Related Articles
- How to Convert Character Set and Collation of WordPress Database
- Download Previous or Old Version of WordPress
- How to Customize, Modify or Change WordPress Database Connection Error Page
- Download WordPress 2.3 Release Candidate 1 (RC1) with Tags Support
- Integrate WordPress including Comments with bbPress Forum using bbSync
- WordPress 2.1.1 Critical Security Alert - Download Upgrade to 2.1.2
- Automatically Update WordPress to Latest Version with Automatic Upgrade Plugin (WPAU)
- Disable Auto Go To (Jump) To Read More Tag
- 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

































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!