Posted by Josh Benner on February 11, 2008 at 10:51pm
Jump to:
| Project: | Multiple E-mail Addresses |
| Version: | 6.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Right now if a user attempts to register with an email address that another user has added to their email addresses but has not yet confirmed, the new user's registration is blocked. This behavior must be changed to one of the following:
- Cancel the pending confirmation and allocate the email address to the new user
- Take new registrant to another page confirming that they actually wish to register a new account, then proceed with item #1 above
Comments
#2
I'm going to bump this issue to 6.x because it still applies. It might be a good idea to have Cron remove unconfirmed emails after a given amount of time, say, 24 hours or so. That would help this issue.
Open to discussion.
#3
@sdboyer recommends adding a "If you received this message in error, click this link and your email will be removed from our system." to the confirmation message.
#4
Duh. There already is a setting for how long unconfirmed emails sit before they expire. That should solve the main problem.
Adding the removal language to the confirmation email is still a good idea.
#5
Not fully the same issue. Situation: Someone registers and adds an email which is not his for whatever reason. This makes it impossible for the other user which owns the real email to register. It should be possible to register even if the email is already taken on an unconfirmed user. If the email gets confirmed only then the other email should be removed.
BTW if we think having duplicate emails as non primary should not be allowed, what would be the extensive rationale behind this decision?
#6
Subscribing. I concur with the behavior described by cor3huis in #5.
I think the CCK filters provided by this module should also allow you to filter by only confirmed addresses as well.