'Django Allauth - allow to sign up again if email is unverified
Suppose, user A tries to sign up with an email not of their own (user's B email). He fails to verify it and hence fails to sign in. Some time later user B encounters the site and tries to sign up, but they fail as well with a message "A user is already registered with this e-mail address." From what I see in admin site, it is true, the user instance is actually created, even though the email is unverified. Is there a way to easily allow user B to sign up (i.e. overwrite the unverified user instance)? Or what is the standard way of dealing with this situation?
Solution 1:[1]
That user will always be in the database in an "unverified" state unless you delete it. One option would be to run a cron job daily or weekly that deletes users that are unverified for over a certain amount of time.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | pycode81 |