-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
discuss and document the future of django-registration #182
Comments
If there was an easy, proven data migration path from this to the other, it might actually happen. |
You could also point people back to the original django-registration which is maintained again. |
@timgraham do you have first hand experience with that package? I do not, so would not want to strongly recommend it like I do django-allauth. |
It's the original project from which django-registration-redux was forked. James Bennett is a Django core developer, so I think it's trustable. |
Newbie here, but something I'd find useful is how to add your own custom fields to the registration page. Let's say things like age or favourite band. Perhaps this is quite obvious for seasoned developers but for me it's going to take a bit of work subclassing forms or overriding URLs. Thanks. |
@charliedontsurf we have a small snippet about multiple form inheritance does that help? |
The maintainers of this project have discussed its future and agree that, in general, django-allauth is a better solution to Django User registration for those looking to adopt something.
However, we do not intend to stop maintaining this project. Our current goal is to continue supporting bug fixes, security fixes, enhancements, and new work from contributors, but to strongly suggest new adopters to look at django-allauth.
This is related to #181
The text was updated successfully, but these errors were encountered: