Facebook registration with an already-taken email. about django-allauth HOT 3 CLOSED

What signup error are you referring to? Currently, the user is forwarded to a signup form allowing him to alter the username/e-mail as retrieved from Facebook. If the user proceeds without altering the e-mail address, the signup form won't validate, stating:

"A user is registered with this e-mail address. "

From here, it is up to the user whether or not he signs in via the already existing account, or whether he wants to proceed and create a new account. In the latter case, he could alter his e-mail adress to do so.

If I understand you correctly, you don't want to offer the user this choice and always force him to sign in to his previous account, right?
If so, what would the rationale be for limiting the user's choices?

from django-allauth.

Closing...

from django-allauth.

I, too, am having problems with this form validation message. Because some users won't understand the fact that they have to sign in ordinarily and connect their account with a social network in order to use it to sign in, a rephrasing of the message would help a lot:

A user is already registered with this e-mail address.

should be changed to

This email address is already in use. If you already have an account on this site, please sign in and connect it with this social account first.

So, I guess what @tudorprodan is saying is, that the user's choices should not be limited but to explain the rationale behind not letting her or him sign in and joining the accounts automatically.

from django-allauth.