News
django-allauth 0.26.0 released
Posted by Raymond Penners on 2016-07-24
Note worthy changes New providers: Weixin, Battle.net, Asana, Eve Online, 23andMe, Slack Django's password validation mechanism (see AUTH_PASSWORD_VALIDATORS) is now used to validate passwords. By default, email confirmations are no longer stored in the database. Instead, the email confirmation mail contains an HMAC based key identifying the email address to confirm.
Read moredjango-allauth 0.25.2 released
Posted by Raymond Penners on 2016-03-13
Note worthy changes Bug fix release (MemcachedKeyCharacterError: "Control characters not allowed")
django-allauth 0.25.1 released
Posted by Raymond Penners on 2016-03-13
Note worthy changes Bug fix release (AttributeError in password reset view).
django-allauth 0.25.0 released
Posted by Raymond Penners on 2016-03-12
Note worthy changes Many providers were added: Reddit, Untappd, GitLab, Stripe, Pinterest, Shopify, Draugiem, DigitalOcean, Robinhood, Bitbucket(OAuth2). The account connections view is now AJAX aware. You can now customize the template extension that is being used to render all HTML templates (ACCOUNT_TEMPLATE_EXTENSION) In order to be secure by default, users are now blocked from logging in after exceeding a maximum number of failed login attempts (see ACCOUNT_LOGIN_ATTEMPTS_LIMIT, ACCOUNT_LOGIN_ATTEMPTS_TIMEOUT).
Read moredjango-allauth 0.24.1 released
Posted by Raymond Penners on 2015-11-09
Note worthy changes Non-test code accidentally had test packages as a dependency. Backwards incompatible changes Setting a password after logging in with a social account no longer logs out the user by default on Django 1.7+. Setting an initial password and changing the password both respect settings.
Read more