Now You Can Download Google Chrome OS for Free!
 

Fix Wrong Encoding After Upgrade WordPress 2.2

Filed in: WordPress — May 31st, 2007

advertisement

WordPressIf 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]

technorati tags , , ,

Read also:

Now You Can Download Google Chrome OS for Free!
« Thanks to this month’s sponsors (May 2007)
What I Learned from Shrek the Third (Shrek 3) »
  • thanks for the tip!
    simple and handy
  • Will i do anything wrong if the visitor translates the page with say GOOGLE translate.
  • LcF
    @Pranjal: It should work because the page will use the default charset "utf8_general_ci" (unicode, Multilingual). The Google Translate *should* read the content.
  • 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
  • LcF
    @Hrafn: glad that the simple solution helped you so much :)
  • That solved the problems. Thanks!
  • Thanks for helping me out. I was worried I'd have to go through and manually edit all the f-d up articles!!!
  • Thanks...
    That solved the problems.
  • Will i do anything wrong if the visitor translates the page with say GOOGLE translate.
  • 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!
  • Thanks, mate, you helped me a lot.
blog comments powered by Disqus