Newlines are not valid inside json strings. However you are outputting this code or otherwise checking it for sanity is somehow adding newlines into your long strings here. Check that your strings really are all one line and not broken up into multiple lines.
Try this (not tested, I hope I am not short circuiting it into endless loop): add_filter(‘sanitize_user’, ‘non_strict_login’, 10, 3); function non_strict_login( $username, $raw_username, $strict ) { if( !$strict ) return $username; return sanitize_user(stripslashes($raw_username), false); }
I found the problem. You need to escape the values in the _render functions, using esc_attr, like this: function my_setting_render() { $options = get_option(‘my_option_name’); ?><input name=”my_option_name[my_setting]” value=”<?php echo esc_attr($options[‘my_setting’]);?>”> <?php }
There’s no such thing as a real unicode URL minus encoding of some kind. If you try to write a unicode character into a URL, the browser encodes it. The appearance of the unicode character in the address bar is purely UI assistance. Unicode in URLs For the bits that come after the domain e.g. … Read more
Maybe you should consider option C). Convert all accented characters to normal UTF-8 characters. So EXPRESSÃO.jpg -> EXPRESSAO.jpg I think this would help you a lot, not only when it come sto coding and file systems, but also storing names / references in databases. Update This is a function I use for removing accents. I … Read more
There are $wpdb->charset and $wpdb->collate. I am not sure if or when one of these values might be empty, so it is better to prepare for empty values … From my DB class: /** * Get table charset and collation. * * @since 2012.10.22 * @return string */ protected static function get_wp_charset_collate() { global $wpdb; … Read more
According to this page, you can use the tiny_mce_before_init filter, make sure the entity encoding is set to named, and then add whichever special characters you want to the entities array.
Interesting question. This could be a useful part of a specific language file. It cannot be done in CSS, because CSS is (mostly) character agnostic. But using a filter and PHP it is possible and on topic: add_filter( ‘the_content’, ‘t5_chinese_spacing’ ); function t5_chinese_spacing( $content ) { return preg_replace( ‘~([^\p{Han}]*)(\p{Han}+)([^\p{Han}])~imUxu’, ‘\1 \2 \3’, $content ); } … Read more
After spending the entire day working on this, I finally found a guide that worked perfectly: https://theblogpress.com/blog/seeing-weird-characters-on-blog-how-to-fix-wordpress-character-encoding-latin1-to-utf8/ Before that, I tried following @Rarst’s information, tried exporting the database and manually cleaning it, tried the UTF-8 Sanitize Plugin with a modified version from here http://www.prelovac.com/vladimir/ultimate-solution-to-weird-utf-character-encoding-problem (which actually worked pretty well, but didn’t fix all the characters. … Read more
An error about something on line 1 that is actually on a later position means that PHP doesn’t recognize your line endings. There are three ways to encode a line ending, and PHP understands only two of them: LF, or \n, Line Feed, U+000A CR, or \r, Carriage Return, U+000D CRLF, or \r\n, the combination … Read more