Django-allauth-underground

Latest version: v0.1.0

Safety actively analyzes 681874 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 6 of 8

0.14.1

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

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

- PyPi did not render the README.rst properly.


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

None

0.14.0

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

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

- Stuart Ross contributed AngelList support, thanks!

- LinkedIn: profile fields that are to be fetched are now
configurable (``PROFILE_FIELDS`` provider-level setting).

- Udi Oron contributed a Hebrew translation, thanks!

- Add setting ``ACCOUNT_DEFAULT_HTTP_PROTOCOL`` (HTTPS support).

- George Whewell contributed Instagram support, thanks!

- Refactored adapter methods relating to creating and populating
``User`` instances.

- User creation methods in the ``Default(Social)AccountAdapter`` now
have access to the ``request``.


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

- The ``socialaccount/account_inactive.html`` template has been
moved to ``account/account_inactive.html``.

- The adapter API for creating and populating users has been
overhauled. As a result, the ``populate_new_user`` adapter methods
have disappeared. Please refer to the section on "Creating and
Populating User Instances" for more information.

0.13.0

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

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

- Koichi Harakawa contributed a Japanese translation, thanks!

- Added ``is_open_for_signup`` to DefaultSocialAccountAdapter.

- Added VK provider support.

- Marcin Spoczynski contributed a Polish translation, thanks!

- All views are now class-based.

- ``django.contrib.messages`` is now optional.

- "jresins" contributed a simplified Chinese, thanks!


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

- The password reset from key success response now redirects to a
"done" view (``/accounts/password/reset/key/done/``). This view has
its own ``account/password_reset_from_key_done.html`` template. In
previous versions, the success template was intertwined with the
``account/password_reset_from_key.html`` template.

0.12.0

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

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

- Added support for re-authenticated (forced prompt) by means of a
new ``action="reauthenticate"`` parameter to the ``{%
provider_login_url %}``

- Roberto Novaes contributed a Brazilian Portuguese translation,
thanks!

- Daniel Eriksson contributed a Swedish translation, thanks!

- You can now logout from both allauth and Facebook via a
Javascript helper: ``window.allauth.facebook.logout()``.

- Connecting a social account is now a flow that needs to be
explicitly triggered, by means of a ``process="connect"`` parameter
that can be passed along to the ``{% provider_login_url %}``, or a
``process=connect`` GET parameter.

- Tomas Marcik contributed a Czech translation, thanks!


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

- The ``{% provider_login_url %}`` tag now takes an optional process
parameter that indicates how to process the social login. As a
result, if you include the template
``socialaccount/snippets/provider_list.html`` from your own overriden
``socialaccount/connections.html`` template, you now need to pass
along the process parameter as follows:
``{% include "socialaccount/snippets/provider_list.html" with process="connect" %}``.

- Instead of inlining the required Facebook SDK Javascript wrapper
code into the HTML, it now resides into its own .js file (served
with ``{% static %}``). If you were using the builtin ``fbconnect.html``
this change should go by unnoticed.

0.11.1

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

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

- Released (due to issue in disconnecting social accounts).

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

None

0.11.0

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

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

- Moved logic whether or not a social account can be disconnected
to the ``SocialAccountAdapter`` (``validate_disconnect``).

- Added ``social_account_removed`` signal.

- Implemented CSRF protection
(http://tools.ietf.org/html/draft-ietf-oauth-v2-30section-10.12).

- The ``user_logged_in`` signal now optionally receives a
``sociallogin`` parameter, in case of a social login.

- Added ``social_account_added`` (contributed by orblivion, thanks).

- Hatem Nassrat contributed Bitly support, thanks!

- Bojan Mihelac contributed a Croatian translation, thanks!

- Messages (as in ``django.contrib.messages``) are now configurable
through templates.
- Added support for differentiating e-mail handling (verification,
required) between local and social accounts:
``SOCIALACCOUNT_EMAIL_REQUIRED`` and
``SOCIALACCOUNT_EMAIL_VERIFICATION``.


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

None

Page 6 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.