Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Duplicate Email Check
Duplicate Email Check
0
Comments
Does this check for duplicate usernames, emails or both?
While I do think it's essential, I can think of a couple scenarios where it wouldn't be best added to the core: A support team that uses Vanilla for product support all shares the same email box, and a online game that allows role-players multiple accounts. Plus, I can't help but realize that Vanilla got along fine for more than two years without this, and only one user requested it (AFAIK).
So maybe just bundle this with the core?
Good point on the exceptions though. I suppose it depends on the forum in question as to whether you want to allow it or not.
"option that's off by default" sounds reasonable to me.
by the way, this duplicate email check is excellent!
I wonder if this extension is still needed and works with the current version of Vanilla? I am getting this error when it finds a duplicate email address.
Undefined variable: UserNamager default.php on line 26
Trying to get property of non-object default.php on line 26
Trying to get property of non-object default.php on line 26
Thanks!
Dan
Will make the corrections and give it another go!
Dan
Consider that the core app permits users to change their email address
(via Account tab >> Personal Information)
I checked the roles/permissions page and don't see a way to disallow this
Seasoned trolls and seasoned spammers often register using their "real" email address (in case receiving/pasting an "email verification code" is required to activate the account) then later, prior to (or immediately after) misbehaving, they edit their account details -- placing a bogus email address into their account info.
When you ban the account, they're back in business 15 minutes later -- able to use that same (initial) email address during subsequent account registration.
To preclude this scenario, the app needs to utilize an additional "prior email" user field, appending (concatenating) the previously active email address into this field each time a user updates his current email address...
...and (ideally) your extension would perform the check against the addresses contained in both (current and prior email) fields.
kandina: I really like that email history idea.
since the version 1.1 update there's been some issues.
First, I simply can't get it to work if there are no other errors during the register process. Line #19 seems to be the problem, as it works fine without this line. Can you check it out.
also on line #32 the redirect to forgot password isn't working. I changed 'PostBackAction=PasswordResetForm&Username=' to 'PostBackAction=PasswordRequestForm&Username=' and it worked then. Is that okay?
and I noticed there was no '?>' at the close of the page; is that important?
thanks again for this great extension, hope this helps with some bugs.
Thanks.