Fincity-django-allauth

*******************

Note worthy changes
-------------------

- ``sourenaraya`` contributed Mail.Ru support, thanks.

- account: Justin Michalicek contributed support to control
session life time and age: ``ACCOUNT_SESSION_COOKIE_AGE`` and
``ACCOUNT_SESSION_REMEMBER``.

- Serafeim Papastefanos contributed an Ukrainian translation,
thanks!

- ``kkarwows`` contributed AppConfig support, thanks.

- socialaccount: Added Xing provider.

- socialaccount: Marcin Skarbek contributed Hubic support, thanks!

- Volodymyr Yatsyk contributed an Ukrainian translation, thanks!

- ``joke2k`` contributed an Italian translation, thanks!

- socialaccount: All providers now support the ``VERIFIED_EMAIL``
property have e-mail addresses forced to be interpreted as
verified.


Backwards incompatible changes
------------------------------

None

*******************

Note worthy changes
-------------------

- Facebook login via Javascript was broken if ``auth_type`` was not
set to ``reauthenticate``, fixed.
- Support for hooking up a callback when ``FB.init()`` is ready
(``allauth.facebook.onInit``)

Backwards incompatible changes
------------------------------

None

*******************

Note worthy changes
-------------------

- Nariman Gharib contributed a Persian translation, thanks!

- The custom signup form ``save`` has been deprecated in favour of a
``def signup(request, user)`` method.

- Facebook reauthentication now uses an ``auth_nonce``.

- Added a new option ``ACCOUNT_LOGIN_ON_EMAIL_CONFIRMATION``, to
indicate whether or not e-mail confirmation is to automatically
log in.

- socialaccount: Added Bitbucket provider.

- Jack Shedd contributed Tumblr support, thanks!

- Romanos Tsouroplis contributed Foursquare support, thanks!

- "excessivedemon" contributed Flickr support, thanks!

- Luis Diego García contributed Amazon and Paypal support, thanks!

- Stuart Ross contributed LinkedIn OAuth 2.0 support, thanks!


Backwards incompatible changes
------------------------------

- Previously, the ``save(user)`` was called on the custom signup form.
However, this shadowed the existing ``save`` method in case a model
form was used. To avoid confusion, the ``save`` method has been
deprecated in favour of a ``def signup(request, user)`` method.

- The Amazon provider requires more space for ``token_secret``, so the
maximum length restriction has been dropped. Migrations are in
place.

*******************

Note worthy changes
-------------------

- socialaccount: Added ``is_auto_signup_allowed`` to social account
adapter.

- facebook: Added a new setting: VERIFIED_EMAIL.

- socialaccount: a collision on e-mail address when you sign up
using a third party social account is now more clearly explained:
"An account already exists with this e-mail address. Please sign
in to that account first, then connect your Google account".

- account: You are now automatically logged in after confirming
your e-mail address during sign up.

- account: The ``/accounts/login/`` view now supports AJAX requests.

- facebook: The fbconnect.js script is now more pluggable.

- socialaccount: Markus Kaiserswerth contributed a Feedly
provider, thanks!

- socialaccount: Dropped django-avatar support.

- openid: First, last and full name are now also queried together
with the e-mail address. Thanks, andrvb.

- openid: Compatibility fix for Django 1.6 (JSON serializer).

- account: Added support for ``ACCOUNT_CONFIRM_EMAIL_ON_GET``.


Backwards incompatible changes
------------------------------

- Instead of directly rendering and returning a template, logging in
while the account is inactive or not yet confirmed now redirects to
two new views: ``/accounts/inactive/`` respectively
``/accounts/confirm-email/``.

- The ``account/verification_sent.html`` template no longer receives the
e-mail address in the context (``email``). Note that a message
containing that e-mail address is still emitted using the messages
framework.

- The ``/accounts/confirm_email/key/`` view has been
renamed to ``/accounts/confirm-email/`` (human friendlier). Redirects
are in place to handle old still pending confirmations.

- Built-in support for django-avatar has been removed. Offering such
functionality means making choices which may not be valid for
everyone. For example, allauth was downloading the image (which can
take some time, or even block) in the context of the login, whereas
a better place might be some celery background job. Additionally, in
case of an error it simply ignored this. How about retries et al?
Also, do you want to copy the avatar once at sign up, or do you want
to update on each login? All in all, this functionality goes way
beyond authentication and should be addressed elsewhere, beyond
allauth scope. The original code has been preserved here so that you
can easily reinstate it in your own project:
https://gist.github.com/pennersr/7571752

*******************

Note worthy changes
-------------------

- Compatibility fix for logging in with Django 1.6.

- Maksim Rukomoynikov contributed a Russian translation, thanks!


Backwards incompatible changes
------------------------------

- In case you were using the internal method
``generate_unique_username``, note that its signature has changed. It
now takes a list of candidates to base the username on.

*******************

Note worthy changes
-------------------

- PyPi did not render the README.rst properly.


Backwards incompatible changes
------------------------------

None