You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider a user has an existing account in a Django site using a Google email. The site enables logging in via Google account with allauth. This will trigger the socialaccount/signup.html page, because the email address on the Google account matches an existing email on an account. However, the user must first submit the signup form, before seeing the error message that an existing account is using that email.
I would propose a behavior change in the previous scenario, where the user gets redirected to the login page with the error about an existing account with {{ email }}.
The text was updated successfully, but these errors were encountered:
This is admittedly an edge case.
Consider a user has an existing account in a Django site using a Google email. The site enables logging in via Google account with allauth. This will trigger the socialaccount/signup.html page, because the email address on the Google account matches an existing email on an account. However, the user must first submit the signup form, before seeing the error message that an existing account is using that email.
I would propose a behavior change in the previous scenario, where the user gets redirected to the login page with the error about an existing account with
{{ email }}
.The text was updated successfully, but these errors were encountered: