Releases: apragacz/django-rest-registration
Releases · apragacz/django-rest-registration
0.3.12
Changes:
- Resolved #22: Sending HTML verification emails
- Resolved #23:
Added CHANGE_PASSWORD_SERIALIZER_PASSWORD_CONFIRM
setting
0.3.9
Changes:
- Resolved #21: Added
REGISTER_OUTPUT_SERIALIZER_CLASS
setting
- Resolved #12: Added verification_redirects Django app
- Resolved #19: Added
LOGIN_SERIALIZER_CLASS
rest_registration setting
0.3.8
Changes:
- Allowing only verified users to register email or reset password
- Resolved issue #16: added
revoke_token
option
- Using py.test and tox for testing
- Fixed issues with renderers:
_get_serializer
passes the params to serializer class
- Fixed url patterns
0.3.7
Changes:
- Fixed issue #8 - Schemas not showing up in django-rest-swagger
- Fixed issue #9 - Register view was able to create user without email with email verification enabled
0.3.6
Changes:
- added app name and view names in urls.py
0.3.5
Changes:
- Added
REGISTER_SERIALIZER_PASSWORD_CONFIRM
field to REST_REGISTRATION
settings to potentially disable password_confirm
field in DefaultRegisterUserSerializer
(issue #2, #3).
0.3.4
Changes:
- fixed unnecessary verification URL escaping in email templates
- fixed sending verification URL to new email instead to the old one in
register_email
0.3.3
Changes
- Adding missing template files in sdist package
0.2.4
Changes
- Adding missing template files in sdist package
0.3.0
Changes
- Fixed problems with tests after changes introduced in Django 1.11 (Issue #1)
- Fixed
is_authenticated
attribute change introduced in Django 1.10, which breaks compatibility in Django 2.0