django-allauth

问题 I have two different user groups group_a and group_b. On register a user can choose the group he/she belongs to. I am using Django Allauth to handle all the user stuff so I've made a custom account adapter to handle the extra logic: custom_adapter.py class UserAccountAdapter(DefaultAccountAdapter): def save_user(self, request, user, form, commit=True): user = super(UserAccountAdapter, self).save_user(request, user, form, commit=False) user.voornaam = form.cleaned_data.get('first_name') user

问题 Signals page for django-allauth: https://django-allauth.readthedocs.io/en/latest/signals.html I am trying to hook the email_verified signal: allauth.account.signals.email_confirmed(request, email_address) And am getting nothing whenever a user confirms their email. Here is my code: from allauth.account.signals import email_confirmed from channels import Group def send_to_user_socket(sender, **kwargs): Group('%s.get-started' % (kwargs['request'].user.username)).send({'text': json.dumps({

问题 Is there anyway to prevent the Allauth Signup form from automatically logging in the User? I found a similar post here with no answers: prevent user login after registration using django-allauth Thank you. 回答1: You get logged in because this behavior is baked into the signup view of the allauth. When the form is valid, the view calls the function called complete_signup that does two things: Emits the user_signed_up signal Logs a user in To solve this, we need to leave the step 1 and replace

问题 Is there anyway to prevent the Allauth Signup form from automatically logging in the User? I found a similar post here with no answers: prevent user login after registration using django-allauth Thank you. 回答1: You get logged in because this behavior is baked into the signup view of the allauth. When the form is valid, the view calls the function called complete_signup that does two things: Emits the user_signed_up signal Logs a user in To solve this, we need to leave the step 1 and replace

问题 I am having this weird error after the integration with django-allauth successfully running for several days. My approach is similar to this project. https://github.com/aellerton/demo-allauth-bootstrap Instead of the user_name, the email is used here as unique identifier of user. IntegrityError at /accounts/signup/ UNIQUE constraint failed: auth_user.email Request Method: POST Request URL: http://localhost:8080/accounts/signup/ Django Version: 1.8 Exception Type: IntegrityError Exception

问题 I am using django-alluth for authentication/registration on my django app. And I need to create a custom signup form with only one field: email. The password will be generated on the server. Here is a form I have created: from django import forms from users.models import User class SignupForm(forms.ModelForm): email = forms.CharField() class Meta: model = User fields = ['email',] esclude = ['password1', 'password'] def __init__(self, *args, **kwargs): super(SignupForm, self).__init__(*args, *

问题 I have created just a simple django app to login using tweeter, but when i try to login from my app I get this message "You are authenticated as xxx, but are not authorized to access this page. Would you like to login to a different account?" I have tried to login with account I used to create the app and different account, but the result is the same. What could be the solution to this? I am using django and django-allauth library 回答1: To access the Django admin, the user needs is_staff=True

问题 I have created just a simple django app to login using tweeter, but when i try to login from my app I get this message "You are authenticated as xxx, but are not authorized to access this page. Would you like to login to a different account?" I have tried to login with account I used to create the app and different account, but the result is the same. What could be the solution to this? I am using django and django-allauth library 回答1: To access the Django admin, the user needs is_staff=True

问题 I am using Google OAuth for my Django App (via allauth package) I have followed all standard configuration steps. In Google Developer console here's what i have: Authorized JavaScript origins https://example.com Authorized redirect URIs https://example.com/accounts/google/login/callback/ - login fails http://example.com/accounts/google/login/callback/ - login succeeds What i observe that if i have a https redirect URL in Authorized redirect URIs, it does not allow login and it fails with

问题 I am using Google OAuth for my Django App (via allauth package) I have followed all standard configuration steps. In Google Developer console here's what i have: Authorized JavaScript origins https://example.com Authorized redirect URIs https://example.com/accounts/google/login/callback/ - login fails http://example.com/accounts/google/login/callback/ - login succeeds What i observe that if i have a https redirect URL in Authorized redirect URIs, it does not allow login and it fails with