From ec6b9d6e63cc352052e6a4c4d36d67f6656c43b7 Mon Sep 17 00:00:00 2001 From: Russell Keith-Magee Date: Sat, 12 Sep 2009 23:56:45 +0000 Subject: [PATCH] Fixed #9236 -- Added documentation on the dependencies of the admin. git-svn-id: http://code.djangoproject.com/svn/django/trunk@11543 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/contrib/admin/index.txt | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/docs/ref/contrib/admin/index.txt b/docs/ref/contrib/admin/index.txt index c23a37264b..823ae8bf3f 100644 --- a/docs/ref/contrib/admin/index.txt +++ b/docs/ref/contrib/admin/index.txt @@ -27,19 +27,24 @@ Overview There are five steps in activating the Django admin site: - 1. Add ``django.contrib.admin`` to your ``INSTALLED_APPS`` setting. + 1. Add :class:``django.contrib.admin`` to your :setting:``INSTALLED_APPS`` + setting. - 2. Determine which of your application's models should be editable in the + 2. Admin has two dependencies - :class:``django.contrib.auth`` and + :class:``django.contrib.contenttypes``. 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 admin interface. - 3. For each of those models, optionally create a ``ModelAdmin`` class that + 4. For each of those models, optionally create a ``ModelAdmin`` class that encapsulates the customized admin functionality and options for that particular model. - 4. Instantiate an ``AdminSite`` and tell it about each of your models and + 5. Instantiate an ``AdminSite`` and tell it about each of your models and ``ModelAdmin`` classes. - 5. Hook the ``AdminSite`` instance into your URLconf. + 6. Hook the ``AdminSite`` instance into your URLconf. Other topics ------------