I submit a non-latin string value and it returns like %23%24%%%
urldecode() solves this problem, as suggested by @BrianFegter
urldecode() solves this problem, as suggested by @BrianFegter
I am just wondering if your website language (in backend) is set to ISO 8859-9 (“Latin 5”). You can manualy check and set them inside wp-config.php or if you go into settings->general https://www.tipsandtricks-hq.com/?p=1480
Words with special characters have dissapeared
It’s WordPress. You could hack into wp-includes/formatting.php and comment out the contents of the sanitize_user() function. However, I don’t think that’s a good idea – it may compromize your site’s security, and special characters can always cause trouble… And it’s never a good idea to hack into the core (maybe you can do it also … Read more
If you check the database description you’ll see that the post content column is longtext, which is: A TEXT column with a maximum length of 4,294,967,295 or 4GB (232 − 1) characters. The effective maximum length is less if the value contains multibyte characters. The effective maximum length of LONGTEXT columns also depends on the … Read more
Okay… so just as I was completing this question I figured out the cause. Using Firebug (in Firefox) I would see a lot of errors regarding access to svg and woff and ttf files under /wp-content/ was blocked. Errors like: “NetworkError: 403 Forbidden – https://www.domainname.com/wp-content/plugins/sg-cachepress/css/logo-white.svg” “NetworkError: 403 Forbidden – https://www.domainname.com/wp-content/themes/genesis/lib/css/fonts/genesis-icon.woff” Seeing this, I realised when … Read more
wp-config.php includes scope for settings for “DB_CHARSET” and DB_COLLATE. Are those settings operative? How do they correspond to the your actual database settings. If the config settings are operative, it might you might try it with them commented out. Edit: On reflection/research, I would set the db_charset and db_collate settings. There are other possibilities (such … Read more
You can try commenting out the encoding type in the wp-config. Sometimes that works. //define(‘DB_CHARSET’, ‘utf8’); //define(‘DB_COLLATE’,’utf8_unicode_ci’);
Checking to length and limiting it is no problem, but as you set the category when you save the post setting different limits per category would be a bit trickier. Below are the steps you would need to take: checking the $post var make it mandatory that a user selects a category seeing what cat … Read more
Don’t think so after skimming through the wptexturize() code, but what about using the run_wptexturize filter (untested): // Turn off wptexturize add_filter( ‘run_wptexturize’, ‘__return_false’ ); // Your text handling here … $text = apply_filters( ‘the_content’, $text ); // Remove filter remove_filter( ‘run_wptexturize’, ‘__return_false’ ); i.e. just turn off the wptexturize only for your text handling?