Please Log in to join the conversation.
I'm very happy to see the new area on CB fields called "Forbidden Words." I've been lobbying for username character restrictions and this feature is close to doing the trick which my JS hacked CB core file used to do.
The problems:
1. To put in a word or character which is forbidden when editing a cb field requires you to put commas between. What if you want the comma itself to be forbidden? I tried 3 commas in a row but that didn't do it. Names like "tonr,f" are allowed but I don't want the comma to be allowed.
2. This character "<" doesn't register in the forbidden words. If I put that character in as forbidden, I can still register a name like "tonr<f" and the ajax checker says "the username tonr" is free..."
That being said, the forbidden character ">" is forbidden fine. If I register the name "tonr>f" the ajax checker comes back and says the input value is not authorized like it should.
3. Typing in these two characters as forbidden: the single quote and double quote, result in a backslash then quote in the field after saving, which I understand. These forbidden characters are correctly forbidden, but it may be confusing for some.
4. Backslash BUG!!! If you have a backslash in the forbidden words field, EVERY TIME you save it the backslashes are doubled!
EG: I just had this in the forbidden field: \\\\\\\',\\\\\\\"
I just hit save and now I have this:
\\\\\\\\\\\\\\\',\\\\\\\\\\\\\\\"
If I save again I get:
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\',\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"
Post edited by: mediaguru, at: 2008/08/10 04:07
Post edited by: mediaguru, at: 2008/08/10 04:10
Please Log in to join the conversation.
Will look into this.
BTW - your sig wish list can be updated.
Upload at registration
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.