django-allauth 0.19.0 released

Posted by Raymond Penners on 2015-01-04

Note worthy changes

Basil Shubin contributed an Odnoklassniki provider, thanks!
Facebook: If the JS SDK is not available, for example due to a browser plugin like Disconnect.me that blocks it, login falls back to the regular non JS handshake.
is_safe_url can now be overridden
Facebook: The Graph API version is now configurable via SOCIALACCOUNT_PROVIDERS.
A Firefox Accounts provider was added by Jannis Leidel, thanks!
Josh Owen contributed Coinbase support, thanks!
Tomas Babej contributed a Slovak translation, thanks!
Moved existing migrations into south_migrations
"zbryikt" contributed a Taiwanese Chinese translation, thanks!
Added support for custom password rules via clean_password.

In the upcoming Django 1.8 it is no longer possible to hookup an unsaved User instance to a SocialAccount. Therefore, if you are inspecting the sociallogin object, you should now use sociallogin.user instead of sociallogin.account.user.
When users logged in while User.is_active was False, they were sent to /accounts/inactive/ in case of a social login, and received a form validation error in case of a local login. This needless inconsistency has been removed. The validation error no longer appears and local logins are also redirected to /accounts/inactive/.
In case you were overriding the ResetPasswordForm: the save method now takes request as its first argument.
All existing migrations have been moved into south_migrations packages, this in order not to conflict with Django's built-in support for migrations. South 1.0 automatically picks up this new location. Upgrade South if you are still dependent on these migrations.