well that's not really the point, of course a workaround would be to forbid multiple account on the same email. I don't feel it is good to add a limitation just to avoid a little bug that should be easy to correct. [originally posted on jforum.net by pala]
This subject is moving to "multiple account single email topic" now apparently.
Remember that you can chose not to check the email, in that case creating lots of bogus adresses is really easy, just type it.
On the other hand I have a case where there a legitimate multiple account/email:
My forum is a forum for a game, some people tend to use the forum as an extension to the game so they login as their game's character. Some may have multiple character in the game and so have multiple accounts on the forum.
I guess that what we are asking is.
-bugless password recovery
-checkbox in admin panel to say "no duplicate email"
Raphael: I didn't put the bug in JIRA since I have only version 2.1.4 If you confirm that it still stands in 2.1.6 I can had it, if you haven't already done that.
A good reason to not allow multiple accounts with the same email is for security .. or to keep people off that are abusing or spamming your forum.
By making them use a different email address with each new username on the forum, it makes it harder for spammers and/or abuses to create multiple new accounts to log in under - they have to use up an email account for each one. Does this keep them from doing it? No, but it does make them expend more effort to keep coming back.
Personally, I think there should NOT be multiple accounts tied to a single email, and the system should prevent someone from changing their email to one that is already used in the system.
as if i knew what I were talking about, I think the confusion here is that we're really discussing a design choice (uid=email addr) where no error condition has been coded apparently to deal with your situation.
So tho it is and isn't a bug, I now see your point in wishing to have that feature. Maybe other forums have it too.
Your request to make that an option sounds great.
<edit>...I guess it is not uid=email, and tho I could look in the code was just trying to say it will probably take some bit of re-design</edit> [originally posted on jforum.net by ken0]
...it is a bit more user input to filter and deal with. with that, it's possible to write several lines in a db/hibernate query where each uid equals a line of hack code. but I figure it could also be dealt with securely :?:
too bad more jforum members aren't developers, incl me. sorry not to help. [originally posted on jforum.net by ken0]