ok so finally found a solution to this. i had to edit class-wp-editor.php and include the following for the $first_init array ‘setup’ => ‘function(ed) { ed.onGetContent.add(function(ed, o) { // Replaces all a characters with b characters o.content = o.content.replace(/\\\\/g, “\”); }); }’,
filter wptexturize doesn’t work on old posts titles
Uncommented constant db define(‘DB_CHARSET’, ‘utf8’) in config.php file
Somehow your files get broken. It can be UTF8 encoding problem, hacker attack, broken plugin. It’s difficult to say what happend without checking your files and log. I recommend you to backing up all files&database , deactivate all plugins and themes and update manually by following this guide : codex.wordpress.org/Updating_WordPress#Manual_Update
Remove the filter wptexturize, which is what’s causing your encoding issue: remove_filter( ‘the_title’, ‘wptexturize’ ); while ( $loop->have_posts() ) { // Your code }
Migrating a WordPress site has broken UTF8 encoding
Try using urldecode on search string and your operations on decoded string. Also check if you are using any other encoding, utf-8, utf-16…..
Still no idea that why and how this happened all of sudden. But here is the 2 Solutions I found which is working: Applying anyone will work 1. Comment these two – //define(‘DB_CHARSET’, ‘utf8’) and //define(‘DB_COLLATE’, ”) 2. Use Latin1, (‘DB_CHARSET’, ‘latin1’) However, I am suspecting some attacks on our sever where blogs are hosted … Read more
ok! seems to have it fixed only by choosing Character set of the file latin1 while importing backed up database something mentioned by @chris-o here Faulty restore of the database, encoding issue
Maybe it is caused by commenting out the charset meta tag? You should have this in your header: <meta charset=”utf-8″ /> You can see in your source that this meta tag is commented out – maybe while debugging this problem. <!–<meta charset=”UTF-8″>–> Additionally you could check if your database settings are set to utf8_general_ci or … Read more