The release of is not compatible with the legacy django-registration (previously maintained by James Bennett). Major backwards incompatible changes will be recorded here, but for a full list of changes between versions you should refer to the CHANGELOG.
As of , requires Django 1.11 or newer; older Django releases may work, but are officially unsupported. Additionally, officially supports Python 2.7, 3.5, 3.6, 3.7 and 3.8.
- None
- None
- None
- None
- None
- None
- None
- None
- Removed support for Django < 1.11.
- Removed registration/urls.py in favor of registration/backends/default/urls.py
- Change of return signature of
RegistrationProfileManager.activate_user
. A tuple containing the User instance and a boolean of whether or not said user was activated is now returned.
- None
- None
- None
- Support for Django 1.7 is removed, and Django 1.8 or newer is required.
- Change signature of
RegistrationProfileManager.activate_user
.site
is now a required positional argument. See #244.
- Remove unnecessary _RequestPassingFormView. See #56. Please ensure that you update any subclassed views to reference
self.request
instead of acceptingrequest
as an argument.
- Django 1.7 or newer is required. Please ensure you upgrade your Django version before upgrading.
Native migration support breaks South compatibility: An initial native migration for Django > 1.7 has been provided. South users will need to configure a null migration with (SOUTH_MIGRATION_MODULES) in settings.py as shown below:
SOUTH_MIGRATION_MODULES = { 'registration': 'registration.south_migrations',
- register method in RegistrationView has different parameters: The parameters of the`register` method in RegistrationView have changed.
- base.html template required: A base.html template is now assumed to exist. Please ensure that your project provides one for to inherit from.
- HTML email templates: now uses HTML email templates. If you previously customized text email templates, you need to do the same with the new HTML templates.