django-allauth: how to properly use email_confirmed signal to set user to active

Question

In another post, I mentioned that I was trying to use allauth's email_confirmed signal to change the is_active field on the confirmed user to true. However, the following code gave me the exception "User matching query does not exist." ``` from allauth.account.signals import email_confirmed from django.dispatch import receiver from django.contrib.auth.models import User @receiver(email_confirmed) def email_confirmed_(request, email_address, **kwargs): user = User.objects.get(email=email_address) user.is_active = True user.save() ``` I tried to re-work this, and still got a similar exception, "EmailAddress matching query does not exist." ``` from allauth.account.signals import email_confirmed from django.dispatch import receiver from django.contrib.auth.models import User from allauth.account.models import EmailAddress @receiver(email_confirmed) def email_confirmed_(request, email_address, **kwargs): new_email_address = EmailAddress.objects.get(email=email_address) user = User.objects.…

Accepted Answer

Turns out the email_address returned by the email_confirmed signal isn't actually a string containing the address, but an object -- allauth.account.models.EmailAddress. This wasn't very clear at all from the documentation, but glad it's resolved now. The code that ended up working was:

```
@receiver(email_confirmed)
def email_confirmed_(request, email_address, **kwargs):

user = User.objects.get(email=email_address.email)
    user.is_active = True

user.save()
```

django-allauth: how to properly use email_confirmed signal to set user to active

Solution

Problem

Related problems