From e5baa07ffcb5f1e54a040553902a2675f18e916a Mon Sep 17 00:00:00 2001 From: Stephen McDonald Date: Sun, 25 Dec 2011 07:30:07 +1100 Subject: [PATCH] Removed SOCIAL_AUTH_IMPORT_BACKENDS from docs as its deprecated. --- README.rst | 15 +++------------ doc/configuration.rst | 11 +---------- 2 files changed, 4 insertions(+), 22 deletions(-) diff --git a/README.rst b/README.rst index 5626fc6..9826c29 100644 --- a/README.rst +++ b/README.rst @@ -122,15 +122,6 @@ Configuration 'django.contrib.auth.backends.ModelBackend', ) -- The application will try to import custom backends from the sources defined in:: - - SOCIAL_AUTH_IMPORT_BACKENDS = ( - 'myproy.social_auth_extra_services', - ) - - This way it's easier to add new providers, check the already defined ones - in ``social_auth.backends`` for examples. - Take into account that backends **must** be defined in AUTHENTICATION_BACKENDS_ or Django won't pick them when trying to authenticate the user. @@ -295,7 +286,7 @@ Configuration SOCIAL_AUTH_CREATE_USERS = False It is also possible to associate multiple user accounts with a single email - address as long as the rest of the user data is unique. Set value as True + address as long as the rest of the user data is unique. Set value as True to enable, otherwise set as False to disable. This behavior is disabled by default (false) unless specifically set:: @@ -354,7 +345,7 @@ raised. Also a new-user signal (``socialauth_registered``) is sent when new accounts are created:: - from social_auth.signals import socialauth_registered + from social_auth.signals import socialauth_registered def new_users_handler(sender, user, response, details, **kwargs): user.is_new = True @@ -574,7 +565,7 @@ GitHub works similar to Facebook (OAuth). - also it's possible to define extra permissions with:: GITHUB_EXTENDED_PERMISSIONS = [...] - + ------- Dropbox diff --git a/doc/configuration.rst b/doc/configuration.rst index 5b2e02f..5491453 100644 --- a/doc/configuration.rst +++ b/doc/configuration.rst @@ -8,7 +8,7 @@ Configuration 'social_auth' ) -- Add desired authentication backends to AUTHENTICATION_BACKENDS_ setting:: +- Add desired authentication backends to Djangp's AUTHENTICATION_BACKENDS_ setting:: AUTHENTICATION_BACKENDS = ( 'social_auth.backends.twitter.TwitterBackend', @@ -26,15 +26,6 @@ Configuration 'django.contrib.auth.backends.ModelBackend', ) -- The application will try to import custom backends from the sources defined in:: - - SOCIAL_AUTH_IMPORT_BACKENDS = ( - 'myproy.social_auth_extra_services', - ) - - This way it's easier to add new providers, check the already defined ones - in ``social_auth.backends`` for examples. - Take into account that backends **must** be defined in AUTHENTICATION_BACKENDS_ or Django won't pick them when trying to authenticate the user. -- 2.39.5