diff options
| author | rowanv <rrvspam@gmail.com> | 2016-01-24 22:26:11 +0100 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-02-01 10:42:05 -0500 |
| commit | a6ef025dfb2a1d1bd23893408eef6d066fb506d9 (patch) | |
| tree | b29b3624a20cc65184c743102e0f5f620412105f /docs/topics/auth/customizing.txt | |
| parent | 8bf8d0e0ecc1805480deb94feb4675b09d3b3a95 (diff) | |
Fixed #26124 -- Added missing code formatting to docs headers.
Diffstat (limited to 'docs/topics/auth/customizing.txt')
| -rw-r--r-- | docs/topics/auth/customizing.txt | 30 |
1 files changed, 15 insertions, 15 deletions
diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt index 3da3cc6970..a1f99f9140 100644 --- a/docs/topics/auth/customizing.txt +++ b/docs/topics/auth/customizing.txt @@ -289,8 +289,8 @@ example, the following checks if a user may view tasks:: .. _extending-user: -Extending the existing User model -================================= +Extending the existing ``User`` model +===================================== There are two ways to extend the default :class:`~django.contrib.auth.models.User` model without substituting your own @@ -360,8 +360,8 @@ the extra database load. .. _auth-custom-user: -Substituting a custom User model -================================ +Substituting a custom ``User`` model +==================================== Some kinds of projects may have authentication requirements for which Django's built-in :class:`~django.contrib.auth.models.User` model is not always @@ -414,8 +414,8 @@ use as your User model. :class:`~django.db.models.OneToOneField` to ``settings.AUTH_USER_MODEL`` as described below. -Referencing the User model --------------------------- +Referencing the ``User`` model +------------------------------ .. currentmodule:: django.contrib.auth @@ -462,8 +462,8 @@ different User model. .. _specifying-custom-user-model: -Specifying a custom User model ------------------------------- +Specifying a custom ``User`` model +---------------------------------- .. admonition:: Model design considerations @@ -716,8 +716,8 @@ utility methods: * ``o``, ``O``, and ``0`` (lowercase letter o, uppercase letter o, and zero) -Extending Django's default User -------------------------------- +Extending Django's default ``User`` +----------------------------------- If you're entirely happy with Django's :class:`~django.contrib.auth.models.User` model and you just want to add some additional profile information, you could @@ -875,16 +875,16 @@ methods and attributes: (the Django app label). If the user is inactive, this method will always return ``False``. -.. admonition:: ModelBackend +.. admonition:: ``PermissionsMixin`` and ``ModelBackend`` If you don't include the :class:`~django.contrib.auth.models.PermissionsMixin`, you must ensure you don't invoke the permissions methods on ``ModelBackend``. ``ModelBackend`` - assumes that certain fields are available on your user model. If your User - model doesn't provide those fields, you will receive database errors when - you check permissions. + assumes that certain fields are available on your user model. If your + ``User`` model doesn't provide those fields, you will receive database + errors when you check permissions. -Custom users and Proxy models +Custom users and proxy models ----------------------------- One limitation of custom User models is that installing a custom User model |