Is there a known issue with non-Latin characters or Unicode handling in the Restricted Words Filtering rule? Any advice on how to make it work with Russian or other non-English languages?
The Bad Words feature looks for a 1:1 string match between input data and what you have entered. If the input has been URL-encoded or encoded as HTML entities it doesn't match.
This didn't use to be a problem, since the feature was originally intended to block spam submission in contact forms which at the time only accepted plain text. The browser submitted a raw Unicode bytestream which would always match. I can see how this can be a problem when you're using a WYSIWYG editor (like the built-in TinyMCE editor), or when you have a form submitting as a GET request.
I'll address that in the next release. My plan for the next release is beginning of September. As a rule of thumb, I don't make releases in August because most of Europe is on vacation during part of the month.
Is it also possible to export bad words and import them into another Admin Tools installation?
We do have the Export Settings and Import Settings features. In Export Settings set Bad Words to Yes and everything else to No. Then import this file into your other sites.
Take a look at the Admin Tools – Auto-import configuration scheduled task type if you want to semi-automate this process, storing the exported JSON file in a URL accessible to all of your sites.
Take a look at the admintools:export CLI command if you want the export to be automated as well. You can use jq to post-process the export if you want to only include the Bad Words in the exported JSON file.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
