Use the Multibyte String functions, in this case mb_strtoupper(). This is a general rule: in WordPress, output is usually encoded in UTF-8. Avoid single-byte functions like strlen(), substr() and others when there is a better mb_* function.
Do not touch that string. URLs must be percent-encoded, and what you see is the slug for the URL. A browser will display the characters just fine, so don’t worry about the database.
Use the proper charset in you website according with the characters you use, that is the correct solution from my point of view. What your are trying is some work around that don’t fix the real issue. You must note that UTF-8 is the standard enconding recommend for internet nowdays. ISO-8859-1 was considered the standard … 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
Never edit the WordPress core files. Instead you should hook into the pre_comment_content, which is where the comment text from the textarea is being sanitized, before it’s inserted into the database. In the example below preg_replace is used to sanitize the comment text submitted. You should modify the function to fit your needs. function keha_filter_comment( … Read more
SOLUTION: So, it turned out (of course) I myself was causing the problem (…) I am getting the widgets with the ‘the_widget()’ method and sending the instance params along as I go. The params are query-string-style parameters and are of course ‘glued’ together with ampersands. Now , I wasn’t encoding the individual params so the … 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 could use regex to only allow alphanumeric characters. $string = preg_replace(“/[^A-Za-z0-9 ]/”, ”, $string);
This is a filter I use to keep my clients from adding special characters to their filenames, should work for you – you’ll have to reupload the file though. /** /* Sanitize Uploaded Filenames /* @param array $file /* @return array $file */ function sanitize_file_uploads( $file ){ $file[‘name’] = sanitize_file_name($file[‘name’]); $file[‘name’] = preg_replace(“/[^a-zA-Z0-9\_\-\.]/”, “”, $file[‘name’]); … Read more