Fincity-django-allauth

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

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

- Chris Davis contributed Vimeo support, thanks!

- Added support for overriding the URL to return to after
connecting a social account
(``allauth.socialaccount.adapter.DefaultSocialAccountAdapter.get_connect_redirect_url``).

- Python 3 is now supported!

- Dropped dependency on (unmaintained?) oauth2 package, in favor
of requests-oauthlib.

- account: E-mail confirmation mails generated at signup can now
be differentiated from regular e-mail confirmation mails by
placing e.g. a welcome message into the
``account/email/email_confirmation_signup*`` templates. Thanks to
Sam Solomon for the patch.

- account: Moved User instance creation to adapter so that e.g.
username generation can be influenced. Thanks to John Bazik for
the patch.

- Robert Balfre contributed Dropbox support, thanks!

- socialaccount: Added support for Weibo.

- account: Added support for sending HTML e-mail. Add
``*_message.html`` templates and they will be automatically picked
up.

- Added support for passing along extra parameters to the OAuth2
authentication calls, such as ``access_type`` (Google) or
``auth_type`` (Facebook).
- Both the login and signup view now immediately redirect to the
login redirect url in case the user was already authenticated.

- Added support for closing down signups in a pluggable fashion,
making it easy to hookup your own invitation handling mechanism.

- Added support for passing along extra parameters to the
``FB.login`` API call.


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

- Logout no longer happens on GET request. Refer to the ``LogoutView``
documentation for more background information. Logging out on GET
can be restored by the setting ``ACCOUNT_LOGOUT_ON_GET``. Furthermore,
after logging out you are now redirected to
``ACCOUNT_LOGOUT_REDIRECT_URL`` instead of rendering the
``account/logout.html`` template.

- ``LOGIN_REDIRECT_URLNAME`` is now deprecated. Django 1.5 accepts both
URL names and URLs for ``LOGIN_REDIRECT_URL``, so we do so as well.

- ``DefaultAccountAdapter.stash_email_verified`` is now named
``stash_verified_email``.

- Django 1.4.3 is now the minimal requirement.

- Dropped dependency on (unmaintained?) oauth2 package, in favor of
requests-oauthlib. So you will need to update your (virtual)
environment accordingly.

- We noticed a very rare bug that affects end users who add Google
social login to existing accounts. The symptom is you end up with
users who have multiple primary email addresses which conflicts
with assumptions made by the code. In addition to fixing the code
that allowed duplicates to occur, there is a management command
you can run if you think this effects you (and if it doesn't effect
you there is no harm in running it anyways if you are unsure):

- ``python manage.py account_unsetmultipleprimaryemails``

- Will silently remove primary flags for email addresses that
aren't the same as ``user.email``.

- If no primary ``EmailAddress`` is ``user.email`` it will pick one
at random and print a warning.

- The expiry time, if any, is now stored in a new column
``SocialToken.expires_at``. Migrations are in place.

- Furthermore, Facebook started returning longer tokens, so the
maximum token length was increased. Again, migrations are in place.

- Login and signup views have been turned into class-based views.

- The template variable ``facebook_perms`` is no longer passed to the
"facebook/fbconnect.html" template. Instead, ``fb_login_options``
containing all options is passed.

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

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

- account: ``user_signed_up`` signal now emits an optional
``sociallogin`` parameter so that receivers can easily differentiate
between local and social signups.

- account: Added ``email_removed`` signal.

- socialaccount: Populating of User model fields is now
centralized in the adapter, splitting up ``name`` into ``first_name``
and ``last_name`` if these were not individually available.

- Ahmet Emre Aladağ contributed a Turkish translation, thanks!

- socialaccount: Added SocialAccountAdapter hook to allow for
intervention in social logins.

- google: support for Google's ``verified_email`` flag to determine
whether or not to send confirmation e-mails.

- Fábio Santos contributed a Portugese translation, thanks!

- socialaccount: Added support for Stack Exchange.

- socialaccount: Added ``get_social_accounts`` template tag.

- account: Default URL to redirect to after login can now be
overriden via the adapter, both for login and e-mail confirmation
redirects.


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

- ``requests`` is now a dependency (dropped ``httplib2``).

- Added a new column ``SocialApp.client_id``. The value of ``key`` needs
to be moved to the new ``client_id`` column. The ``key`` column is
required for Stack Exchange. Migrations are in place to handle all
of this automatically.

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

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

- Markus Thielen contributed a German translation, thanks!

- The ``site`` foreign key from ``SocialApp`` to ``Site`` has been replaced
by a ``ManyToManyField``. Many apps can be used across multiple domains
(Facebook cannot).

- account: Added adapter class for increased pluggability. Added
hook for 3rd party invitation system to by pass e-mail
verification (``stash_email_verified``). Moved sending of mail to
adapter.

- account: Added option to completely disable e-mail verification
during signup.


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

- The ``ACCOUNT_EMAIL_VERIFICATION`` setting is no longer a boolean
based setting. Use a string value of "none", "optional" or
"mandatory" instead.

- The template "account/password_reset_key_message.txt" has been moved
to "account/email/password_reset_key_message.txt". The subject of
the message has been moved into a template
("account/email/password_reset_key_subject.txt").

- The ``site`` foreign key from ``SocialApp`` to ``Site`` has been replaced
by a ``ManyToManyField``. Many apps can be used across multiple
domains (Facebook cannot).

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

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

- Twitter: Login was broken due to change at in URLs at Twitter,
fixed.

- LinkedIn: Added support for passing along the OAuth scope.

- account: Improved e-mail confirmation error handling, no more
confusing 404s.

- account: Aldiantoro Nugroho contributed support for a new
setting: ACCOUNT_USERNAME_MIN_LENGTH

- socialaccount: Added preliminary support for Mozilla Persona.

- account: Sam Solomon added various signals for email and
password related changes.

- account: Usernames may now contain , +, . and - characters.


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

- Dropped support for ``CONTACT_EMAIL`` from the ``account`` template
context processor. It was never documented and only used in the
templates as an example -- there is no need to pollute the ``allauth``
settings with that. If your templates rely on it then you will have
to put it in a context processor yourself.

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

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

- Python 2.6.2 compatibility issue, fixed.

- The example project was unintentionally packaged, fixed.


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

None

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

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

- account: Dropped dependency on the emailconfirmation app,
integrating its functionality into the account app. This change is
of major impact, please refer to the documentation on how to
upgrade.

- account: Documented ACCOUNT_USERNAME_REQUIRED. This is actually
not a new setting, but it somehow got overlooked in the
documentation.

- account/socialaccount: Dropped the _tags postfix from the
template tag libraries. Simply use {% load account %} and {% load
socialaccount %}.

- Added signup and social login signals.

- SoundCloud: Rabi Alam contributed a SoundCloud provider, thanks!

- account: Sam Solomon cleaned up the e-mail management view:
added proper redirect after POSTs, prevent deletion of primary
e-mail. Thanks.

- account: When signing up, instead of generating a completely
random username a more sensible username is automatically derived
from first/last name or e-mail.


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

- ``allauth`` now depends on Django 1.4 or higher.

- Major impact: dropped dependency on the ``emailconfirmation`` app, as
this project is clearly left unmaintained. Important tickets such
as https://github.com/pinax/django-email-confirmation/pull/5 are not
being addressed. All models and related functionality have been
directly integrated into the ``allauth.account`` app. When upgrading
take care of the following:

- The ``emailconfirmation`` setting ``EMAIL_CONFIRMATION_DAYS`` has been
replaced by ``ACCOUNT_EMAIL_CONFIRMATION_EXPIRE_DAYS``.

- Instead of directly confirming the e-mail address upon the GET
request the confirmation is now processed as part of an explicit
POST. Therefore, a new template ``account/email_confirm.html`` must
be setup.

- Existing ``emailconfirmation`` data should be migrated to the new
tables. For this purpose a special management command is
available: ``python manage.py
account_emailconfirmationmigration``. This command does not drop
the old ``emailconfirmation`` tables -- you will have to do this
manually yourself. Why not use South? EmailAddress uniqueness
depends on the configuration (``ACCOUNT_UNIQUE_EMAIL``), South does
not handle settings dependent database models.

- ``{% load account_tags %}`` is deprecated, simply use: ``{% load account %}``

- ``{% load socialaccount_tags %}`` is deprecated, simply use:
``{% load socialaccount %}``