LiewCF.com

Fix Wrong Encoding After Upgrade WordPress 2.2

Filed in: WordPress — May 31st, 2007

If your non-English WordPress blog has wrong characters encoding after upgrade to WordPress 2.2. Don’t worry. It can be solved easily by editing WordPress configuration file.

1. Open and edit “wp-config.php”
2. Find: define('DB_CHARSET', 'utf8');
3. Remove “utf8″, so it becomes: define('DB_CHARSET', '');
4. Save and upload “wp-config.php”
5. Done. Your WordPress blog should display characters correctly.

By default, if no character set is defined, WordPerss 2.2 will use utf8_general_ci

[source]

2.2, charset, encoding, wordpress

Read also:

• WordPress 2.1.1 and 2.0.9 Bugfix
• Upgrade to WordPress 1.5.2
• Wordpress 1.5.1 Released
• Now, Upgrade to WordPress 1.5.1.3
• Upgraded to WordPress 2.1.2 from 2.0.9

What do you think? 15 Responses to “Fix Wrong Encoding After Upgrade WordPress 2.2”

Comments Feed | TrackBack URL

1. #1
   Andrew Mycah Says:
   May 31st, 2007 at 9:00 pm

   thanks for the tip!
   simple and handy

2. #2
   Pranjal Says:
   June 1st, 2007 at 1:31 pm

   Will i do anything wrong if the visitor translates the page with say GOOGLE translate.

3. #3
   LcF Says:
   June 1st, 2007 at 2:21 pm

   @Pranjal: It should work because the page will use the default charset “utf8_general_ci” (unicode, Multilingual). The Google Translate *should* read the content.

4. #4
   افكار و احلام » WordPress 2.2 and the importance of doing Unicode right, from the start Says:
   June 2nd, 2007 at 2:29 pm

   [...] there seems to be a (fragile?) simple hack to “fix” the problem; the solution was Google’s first hit (now there’s technology working for you!) and the gibberish is banished. [...]

5. #5
   Getting Hebrew to work on WordPress 2.2 » wordpressgarage.com Says:
   June 6th, 2007 at 4:22 pm

   [...] I found the solution! Liew Cheon Fong at LiewCF has nonchalantly posted a simple solution that works, as if it’s not the most brilliant thing ever! (Ok, I exaggerate, but [...]

6. #6
   deb.foocode.net » One Post to Cover Several Says:
   June 24th, 2007 at 11:14 am

   [...] come up with a very simple set of instructions that work! Thanks LiewCF. You can either check out his post or follow his instructions (which I shall repeat) [...]

7. #7
   hthth Says:
   August 14th, 2007 at 12:41 am

   Thanks so much for discovering this solution and sharing it! I was staring down the barrel of manually correcting my posts, but thanks to you everything seems fine now.

   -Hrafn

8. #8
   LcF Says:
   August 14th, 2007 at 1:12 am

   @Hrafn: glad that the simple solution helped you so much

9. #9
   senn Says:
   August 25th, 2007 at 6:15 pm

   That solved the problems. Thanks!

10. #10
    Jiyan Says:
    December 18th, 2007 at 5:08 am

    Thanks for helping me out. I was worried I’d have to go through and manually edit all the f-d up articles!!!

11. #11
    article good Says:
    March 24th, 2008 at 1:57 am

    Thanks…
    That solved the problems.

12. #12
    su deposu Says:
    April 5th, 2008 at 4:54 am

    Will i do anything wrong if the visitor translates the page with say GOOGLE translate.

13. #13
    Ian’s blog » Blog Archive » Characters not showing up Says:
    May 9th, 2008 at 2:25 am

    [...] I needed to do this to make it [...]

14. #14
    Daniel Craig Says:
    July 23rd, 2008 at 11:59 pm

    Hi, I was looking around for a while searching for internet security solutions and I happened upon this site and your post regarding ng Encoding After Upgrade WordPress 2.2, I will definitely this to my internet security solutions bookmarks!

15. #15
    Halibutt Says:
    August 26th, 2008 at 4:14 am

    Thanks, mate, you helped me a lot.

Leave a Reply