I see this often on many blogs and I'm thinking it's a word press bug. You ever notice out of no where all apostrophes used in word press will turn into weird characters? Just search Google for ’ Code (markup): or †Code (markup): Why is this happening? I notice it a lot on my social network for bloggers http://www.blogengage.com/ Simply search that again on my site and I have 24 pages! When searching it on my site you have to add a space before the characters or nothing comes up! Any ideas?
If the issue was on my end why does it only happen to specific articles? If the issue was on my end wouldn't all of the articles be like this?
It could be due to incorrect collation set for your MySQL database but I am not sure. I have two wordpress blogs and didn't face such problem.
I have 4 wordpress blogs I have the issue on one blog at one point! Specifically old blogs or old articles
Usually happens when they've exported out their blog's contents as one charset and imported elsewhere into a database of another charset. Wordpress is setup to work with utf8 but many english language CPanel installs default to latin-something. edit: You're probably seeing it more oftne since wp.com uses utf8 and folks are starting their blogs and elsewhere to their own installs.
Could it still happen if the data was manually imported? We have no auto import.. I don't think anyways!
By importing and exporting, I mean Dashboard -> Manage -? Export/Import. With the XML file you get. Not sure what you mean by manually importing and exporting.
Sorry I mis understood you! I thought you were referring to my sites data and not a wordpess blogs data! All my data on my website is manually entered! Users go though a submit process http://www.blogengage.com
The characters are showing on your site, because pligg doesn't strip out or sanitize the title. An example on your site- Kate Gosselin Speaks, Defends The “Spanking Of Leah On the blog - Kate Gosselin Speaks, Defends The “Spanking†Of Leah You can see Pligg is changing any & " ; characters into these. I would try searching the pligg forum for a solution. In Wordpress version 2.2 this problem showed up in posts. So older posts that never got re-edited the problem is still there in their posts even though their Wordpress is upgraded to the latest. Hope that helps.