IntegrityError on email change if user email field is unique about django-allauth HOT 3 CLOSED

Django has the email field defined like this:

class AbstractUser(AbstractBaseUser, PermissionsMixin):
    email = models.EmailField(_("email address"), blank=True)

You deviate from that by doing:

    email = models.EmailField(_("email address"), blank=False, null=False, unique=True)

So, you're making it unique. When the user model has an email field allauth populates that, even if the email address is still unverified. Note that allauth allows for 2 different users to have the same email address, though only one user can have it listed as verified.

Given your user model definition, I think the only way around would be to not populate the email field for users unless it is truly verified. You could do that by setting ACCOUNT_USER_MODEL_EMAIL_FIELD to None -- then allauth won't do any attempt to populate the field. Then, you could use e.g. the email_confirmed signal to actually start populating the field.

Though, you can also ask yourself, why go against the flow, and why not just use Django's standard way of working? Or, perhaps remove the email field from the user altogether as it really is just denormalized data (of the EmailAddress model).

from django-allauth.

...my assumption would have been that this is intercepted.

As mentioned above, your email field deviates from what is standard in Django, and allauth has no knowledge about how you want to have that populated. So I don't really see how this can be intercepted. Just set ACCOUNT_USER_MODEL_EMAIL_FIELD = None.

from django-allauth.

Hi, thanks for the quick reply. I guess that will help :)

from django-allauth.