mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-04 10:59:45 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Fixed #15757 - removed remaining instances of get_and_delete_messages

Browse source 
Thanks to void for the report, and julien for the bulk of the patch.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@16022 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Luke Plant 2011-04-07 22:01:23 +00:00
parent b7715b4ae6
commit 8d4b414760
8 changed files with 30 additions and 117 deletions
Download patch file Download diff file Expand all files Collapse all files

22
docs/ref/contrib/admin/index.txt
View file

@ -14,26 +14,32 @@ Django's admin interface.
Overview
========
There are six steps in activating the Django admin site:
There are seven steps in activating the Django admin site:
1. Add ``'django.contrib.admin'`` to your :setting:`INSTALLED_APPS`
setting.
2. Admin has two dependencies - :mod:`django.contrib.auth` and
:mod:`django.contrib.contenttypes`. If these applications are not
in your :setting:`INSTALLED_APPS` list, add them.
2. Admin has three dependencies - :mod:`django.contrib.auth`,
:mod:`django.contrib.contenttypes` and :mod:`django.contrib.messages`.
If these applications are not in your :setting:`INSTALLED_APPS` list,
add them.
3. Determine which of your application's models should be editable in the
3. Add ``django.contrib.messages.context_processors.messages`` to
:setting:`TEMPLATE_CONTEXT_PROCESSORS` and
:class:`~django.contrib.messages.middleware.MessageMiddleware` to
:setting:`MIDDLEWARE_CLASSES`.
4. Determine which of your application's models should be editable in the
admin interface.
4. For each of those models, optionally create a ``ModelAdmin`` class that
5. For each of those models, optionally create a ``ModelAdmin`` class that
encapsulates the customized admin functionality and options for that
particular model.
5. Instantiate an ``AdminSite`` and tell it about each of your models and
6. Instantiate an ``AdminSite`` and tell it about each of your models and
``ModelAdmin`` classes.
6. Hook the ``AdminSite`` instance into your URLconf.
7. Hook the ``AdminSite`` instance into your URLconf.
Other topics
------------