diff options
| author | Claude Paroz <claude@2xlibre.net> | 2016-05-15 17:28:00 +0200 |
|---|---|---|
| committer | Claude Paroz <claude@2xlibre.net> | 2016-06-24 10:45:13 +0200 |
| commit | 78963495d0caadb77eb97ccf319ef0ba3b204fb5 (patch) | |
| tree | 52162432f13b92b85b6188a6415887cfc06c5701 /docs/ref | |
| parent | 742ea51413b3aab07c6afbfd1d52c1908ffcb510 (diff) | |
Refs #17209 -- Added LoginView and LogoutView class-based views
Thanks Tim Graham for the review.
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/contrib/auth.txt | 4 | ||||
| -rw-r--r-- | docs/ref/contrib/sites.txt | 4 | ||||
| -rw-r--r-- | docs/ref/settings.txt | 4 |
3 files changed, 6 insertions, 6 deletions
diff --git a/docs/ref/contrib/auth.txt b/docs/ref/contrib/auth.txt index 5836cb329e..91e3fbd1ba 100644 --- a/docs/ref/contrib/auth.txt +++ b/docs/ref/contrib/auth.txt @@ -93,7 +93,7 @@ Fields if you want to allow inactive users to login. In this case, you'll also want to customize the :class:`~django.contrib.auth.forms.AuthenticationForm` used by the - :func:`~django.contrib.auth.views.login` view as it rejects inactive + :class:`~django.contrib.auth.views.LoginView` as it rejects inactive users. Be aware that the permission-checking methods such as :meth:`~django.contrib.auth.models.User.has_perm` and the authentication in the Django admin all return ``False`` for inactive @@ -582,7 +582,7 @@ The following backends are available in :mod:`django.contrib.auth.backends`: When using this backend, you'll likely want to customize the :class:`~django.contrib.auth.forms.AuthenticationForm` used by the - :func:`~django.contrib.auth.views.login` view by overriding the + :class:`~django.contrib.auth.views.LoginView` by overriding the :meth:`~django.contrib.auth.forms.AuthenticationForm.confirm_login_allowed` method as it rejects inactive users. diff --git a/docs/ref/contrib/sites.txt b/docs/ref/contrib/sites.txt index 82fa1e41d5..668744a9c2 100644 --- a/docs/ref/contrib/sites.txt +++ b/docs/ref/contrib/sites.txt @@ -436,8 +436,8 @@ Here's how Django uses the sites framework: the current :class:`~django.contrib.sites.models.Site` object if you don't specify a fully-qualified domain. -* In the :mod:`authentication framework <django.contrib.auth>`, the - :func:`django.contrib.auth.views.login` view passes the current +* In the :mod:`authentication framework <django.contrib.auth>`, + :class:`django.contrib.auth.views.LoginView` passes the current :class:`~django.contrib.sites.models.Site` name to the template as ``{{ site_name }}``. diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt index ab4f9c6efe..f995f4c21d 100644 --- a/docs/ref/settings.txt +++ b/docs/ref/settings.txt @@ -2736,8 +2736,8 @@ the URL in two places (``settings`` and URLconf). Default: ``None`` -The URL where requests are redirected after a user logs out using the -:func:`~django.contrib.auth.views.logout` view (if the view doesn't get a +The URL where requests are redirected after a user logs out using +:class:`~django.contrib.auth.views.LogoutView` (if the view doesn't get a ``next_page`` argument). If ``None``, no redirect will be performed and the logout view will be |
