News
django-allauth 0.31.0 released
Posted by Raymond Penners on 2017-02-28
Note worthy changes Added a new user_logged_out signal. OpenId: Added support for requesting additional data. New providers: Auth0, Box, Line, Naver, Kakao, Daum, MailChimp, Eventbrite. Backwards incompatible changes Django 1.7 / Python 3.2 compatibility has been dropped. Due to providers being registered in the same file as their definition it was impossible to subclass a provider without having the parent be registered.
Read moredjango-allauth 0.30.0 released
Posted by Raymond Penners on 2017-01-01
Note worthy changes Changed the algorithm that generates unique usernames. Previously, in case the provider did not hand over any information to base the username on, the username "user" extended with an ever increasing numeric suffix would be attempted until a free username was found.
Read moredjango-allauth 0.29.0 released
Posted by Raymond Penners on 2016-11-21
Note worthy changes Addressed Django 1.10 deprecation warnings.
django-allauth 0.28.0 released
Posted by Raymond Penners on 2016-10-13
Security notice Previous versions contained a vulnerability allowing an attacker to alter the provider specific settings for SCOPE and/or AUTH_PARAMS (part of the larger SOCIALACCOUNT_PROVIDERS setting). The changes would persist across subsequent requests for all users, provided these settings were explicitly set within your project.
Read moredjango-allauth 0.27.0 released
Posted by Raymond Penners on 2016-08-18
Note worthy changes Django 1.10 compatibility. The Twitter and GitHub providers now support querying of the email address. Backwards incompatible changes When ACCOUNT_SIGNUP_EMAIL_ENTER_TWICE was turned on, the email field key changed from email to email1, which could introduce subtle bugs.
Read more