It seems that the “convert_chars” filter is causing the trouble, try removing it by: remove_filter( ‘the_content’, ‘convert_chars’ ); Also try removing the richedit_pre hook (which formats the text for the rich text editor, also uses convert_chars function) by: remove_filter( ‘the_editor_content’, ‘wp_richedit_pre’ ); Hope that helps!
The problem is an invalid UTF-8 character in the excerpt <description>. The text is cut off in the middle of a multi-byte character, rendering your complete feed invalid. You get a slightly hint when you look at it in Opera. Do you filter ‘bloginfo_rss’ or ‘get_bloginfo_rss’? Disable all plugins and look if the feed is … Read more
This might be a limitation of JavaScript. 𪇆 is U+2A1C6 in Unicode, and codepoints above U+FFFF (which need four bytes) are coded via UTF-16 surrogates. And that … sucks. The canonical bug for that in WordPress is #13590 Inserting a 4-byte UTF-8 character truncates data. It was closed as maybe later, because fixing it would … Read more
Query string becomes encoded when a static page is used as homepage
After trying several times to set the proper charset, I wasn’t successful. Then I searched for an workaround and found one that worked with my problem. In addition to set the charset like I mentioned above, what I did is to convert all strings on my POST body with this php snippet: $message = @iconv(“UTF-8″,”Windows-1252//IGNORE”,$message); … Read more
This is happening due to encoding. I assume you have a function in your search page, which you get and use search_text inside that template. You should decode the URL before doing so. The urldecode() function would be what you are looking for. Your string is also UTF-8 encoded, so this is what you are … Read more
So after about a year (on and off!) I had managed to hopefully get a fix on encoding issue. Why it breaks What my experience boiled down to, is that encoding issue like this are mostly caused by miscommunication when moving data around. in best case this is read mismatch, when correct data is wrongly … Read more
UNIX line endings (\n) and UTF-8 are just common code standards. As far as I can see, they are not even mentioned in the Coding Standards. Most (all?) core PHP files are just plain US-ASCII. Try to follow that path to keep your files as compatible as possible. If you use UTF-8, add a line … Read more
You only have 1 option here, which by most standards isn’t advised. You have to edit a core WordPress file: wp-db.php The reason is that there are no filters to change these and the code is kinda hard-coded. WordPress checks the availability of collation it selects though. If you need it just enough to setup … Read more
What is your database encoding? Try to switch to utf8mb4. Alternatively, try to add one of these lines in your wp-config.php file: define(‘DB_CHARSET’, ‘latin1’); define(‘DB_COLLATE’, ”); or define(‘DB_CHARSET’, ‘utf8’); define(‘DB_COLLATE’, ”); or define(‘DB_CHARSET’, ‘utf8mb4’); define(‘DB_COLLATE’, ”);