21
Thanks very much for all the comments and kudos tklee.
Here's my thoughts...
Quote:
changed? May I suggest wrapping those added codes with a condition statement so if the module is not installed, those codes will get skipped?)
The user account creation form does check to see if the reg_codes datatable exists (ie: the module is installed) and if it does, then the registration code is asked for. If the table does not exist, then the form does not include the box for registration code.
So if you leave the hacked files in place but remove the module, then the account creation process should be exactly as if the hacked files were not present.
Quote:
Registration Keys is admin-only tool so the webmasters have to do everything; Registration Codes provides the "group invitation by group member" function. That's really cool. I also found automatic expiration very useful.
Thanks!
Quote:
About the randomly generated password, I'd suggest it being optional. Making it optional allows us to use meaningful keywords to invite people.
Good point. Security is a big concern for our sites, since clients use them for important, confidential business information, so they didn't want guessable or easily crackable codes, that's why they were made random (though only six characters doesn't make them that hard to crack, but anyway, they're not dictionary words).
I agree though, it would be a good addition if you had the option of typing in a word that you wanted to use for your code. Maybe that will go in a future version.
I've found, among other things, that the registration code box is a required field, so there's no point in having the word 'Optional' beside it. So there's a few polish-related things like that which could go in another release.
Thanks one and all for the interest!
--Julian
