Scotty, I don’t think WLPE can do this yet, but to make this a universal application, maybe in a future version, you could allow for a custom date format. Like having &date=`MM-DD-YYYY` in the WLPE call. Types
profile,
user, and
manage would probably be the only ones who would need this.
Like how the US uses the MM/DD/YYYY format, IIRC, Japan uses DD-MM-YYYY. So having the option to do set that (and have MM-DD-YYYY as a default, I’d assume). That would require having WLPE be able to calculate the age, though, which I’d guess is just tinkering what you already did.
Now, in the case that a site uses DD-MM-YYYY, but uses the English language file (or heck, if someone has a multilanguage site and found a way to get WLPE to pick the correct lang file), have a [+PLACEHOLDERHERE+] in the language file would make it so the person wouldn’t have to go and edit it. You already do it for stuff like the KB user image limit, the failed login count, etc., so this shouldn’t be that hard, in theory anyway.
Sorry if that was semi-confusing. I tried to explain the best I could.
EDIT: I thought of another idea. You know how some sites restrict users below X age? Maybe add a check in the Register code to deny any age below a number set in a config variable like &ageRequired=`13` or &dobRequired=`1-1-1994`, Since WLPE can already get the age from a DOB, I don’t see why it shouldn’t be able to deny a user using that information as well (this might open up the option for a COPPA-type thing, like you see on some forums --- where the under-13 user goes to a seperate register page or something).
EDIT 2: Does WLPE already have an option to limit the number of words in the signature/comment field and/or allow/disallow basic HTML in that field? That might be a good idea to implement if it doesn’t already have it.
