http://www.bioneural.net/feeder/?FeederAction=clicked&feed=Comments+on+Articles+%28RSS2%29&seed=http%3A%2F%2Fwww.bioneural.net%2F2008%2F01%2F18%2Fput-a-stop-to-wordpress-character-replacements%2F%23comment-&seed_title=Stop+WordPress+character+replacements bioneural.net is for stuff worth sharing: commentary by Bruce McKenzie. Major topics covered are gadgets, informatics, Internet, Mac, mobile, musings, New Zealand, photography, Project Koru, quicklinks, rant, rave, travel and Windows Fri, 08 Aug 2008 21:20:53 +0000 http://www.bioneural.net/feeder/?FeederAction=clicked&feed=Comments+on+Articles+%28RSS2%29&seed=http%3A%2F%2Fwww.bioneural.net%2F2008%2F01%2F18%2Fput-a-stop-to-wordpress-character-replacements%2F%23comment-76270&seed_title=Stop+WordPress+character+replacements#comment-76270 Bruce Fri, 18 Jan 2008 21:16:40 +0000 http://www.bioneural.net/2008/01/18/put-a-stop-to-wordpress-character-replacements/#comment-76270 No, this isn't the problem (for certain). Looking at your source Rob I see your blog's character set is set to utf-8, which should handle entities. When comparing files during my WP upgrade I noticed two extra lines in wp-config-sample.php—which weren't there in my older config.php file. I have <a href="http://wordpress.org/support/topic/119998" rel="nofollow">read</a> that deleting these two lines (define('DB_CHARSET', 'utf8'); and define('DB_COLLATE', '');) if you edited them in, or did an automatic upgrade, can resolve problems. Maybe try that if you see these lines in your config file? See the <a href="http://codex.wordpress.org/Editing_wp-config.php" rel="nofollow">Warning for those performing upgrades</a>. Also, at the phpMyAdmin login screen, is your language reported as English (utf-8)? No, this isn't the problem (for certain). Looking at your source Rob I see your blog's character set is set to utf-8, which should handle entities. When comparing files during my WP upgrade I noticed two extra lines in wp-config-sample.php—which weren't there in my older config.php file. I have read that deleting these two lines (define('DB_CHARSET', 'utf8'); and define('DB_COLLATE', '');) if you edited them in, or did an automatic upgrade, can resolve problems. Maybe try that if you see these lines in your config file? See the Warning for those performing upgrades. Also, at the phpMyAdmin login screen, is your language reported as English (utf-8)?

]]> http://www.bioneural.net/feeder/?FeederAction=clicked&feed=Comments+on+Articles+%28RSS2%29&seed=http%3A%2F%2Fwww.bioneural.net%2F2008%2F01%2F18%2Fput-a-stop-to-wordpress-character-replacements%2F%23comment-76266&seed_title=Stop+WordPress+character+replacements#comment-76266 Rob Fri, 18 Jan 2008 20:41:51 +0000 http://www.bioneural.net/2008/01/18/put-a-stop-to-wordpress-character-replacements/#comment-76266 Hmm, could this be why my update of MySQL resulted in a bunch of odd Unicode characters? Hmm, could this be why my update of MySQL resulted in a bunch of odd Unicode characters?

]]>