Open xLink opened 11 years ago
Yeah good idea, I don't see how difficult that would be, but obviously by default needs to just be Upper+Lower (Maybe Digits)
Infact, the default should be \w
How about making an input field and a couple of checkboxes which would on being checked populate the input field with regex. This way both inexperienced users and users who understand regular expression can use such?
the regex options above just represent the options we have availiable, not what will actually show on the users end. we'll come up with better names for em :P
I think what Infy means is that we should give the admins an input field which allows them to put in their custom Regex, so they can specify exactly the patterns that they want, for example: [a-z]{4,} or something similar.
oh i see, overcomplicating things a little i think, im all up for having control, but most systems dont let you do with the username in the first place nvm select the pattern to match it against
@DarkMantisCS Indeed! Experienced users may edit the input field themselves, or it can be manipulated via the checkboxes.
I don't think it's overcomplicated I think its customizable. Imo, it should be implemented
In the ACP I beleive we should be giving the administrator the ability to choose what sets of charaters he wants to allow in the CMS..
The panel could look something like this following ASCII Rendering;
[ ] Upper & Lower case English alphabet ( [a-zA-Z] ) [ ] Digits ( [0-9] ) [ ] "Simple Special Characters" ( [!@#$%^&()<>?:"|{}+_/`] etc ) [ ] "Extended Special Characters" - this will be the foreign language set
The idea here, is to be able to tick what you want to allow, the functionality should take this into account when testing a username being valid, and any escaping should be done to make sure no vulnerabilities either client or server side.
Thoughts?