CB provides a means to declare comma-delimited "bad words" (from whatever source) as text field parameters for reg and profile edits.
However, those words turn out to be managed as substrings as well and not only as comma-delimited words.
A lot of of my members were simply unable to register their address.
Why? Forbidden word "ass" is a substring of "Strasse" which means "street" in german.
I think to consider forbidden words as a substring of any word is too restrictive.
Who has experience implementing "bad words" and to spend some thoughts about to handle this?
If any occurrence of the word appears in the supplied string it will error. It's not breaking the input into words then checking each word individually. We have no such usage. Suppose you could use CB Code Field, which provides a Code validation usage where you can supply your own PHP for validating a fields value and there you could add your word by word validation.
Kyle (Krileon) Community Builder Team Member Before posting on forums:
Read FAQ thoroughly
+
Read our Documentation
+
Search the forums CB links:
Documentation
-
Localization
-
CB Quickstart
-
CB Paid Subscriptions
-
Add-Ons
-
Forge
-- If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
-- If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please
send me a private message
with your thread and will reply when possible!
-- Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
-- My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.
krileon
