From c2ee295f502295ac8b53d6d31ad492e831d3519c Mon Sep 17 00:00:00 2001 From: Brian Rosner Date: Sun, 20 Jul 2008 18:20:54 +0000 Subject: [PATCH] Fixed #7850 -- Added adding django.contrib.admin to INSTALLED_APPS to the steps to activating the Django admin site. Thanks dacort for the report. git-svn-id: http://code.djangoproject.com/svn/django/trunk@8010 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/admin.txt | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/docs/admin.txt b/docs/admin.txt index 2eeaa64628..431fa4e0b9 100644 --- a/docs/admin.txt +++ b/docs/admin.txt @@ -18,19 +18,21 @@ Django's admin interface. Overview ======== -There are four steps in activating the Django admin site: +There are five steps in activating the Django admin site: - 1. Determine which of your application's models should be editable in the + 1. Add ``django.contrib.admin`` to your ``INSTALLED_APPS`` setting. + + 2. Determine which of your application's models should be editable in the admin interface. - 2. For each of those models, optionally create a ``ModelAdmin`` class that + 3. For each of those models, optionally create a ``ModelAdmin`` class that encapsulates the customized admin functionality and options for that particular model. - 3. Instantiate an ``AdminSite`` and tell it about each of your models and + 4. Instantiate an ``AdminSite`` and tell it about each of your models and ``ModelAdmin`` classes. - 4. Hook the ``AdminSite`` instance into your URLconf. + 5. Hook the ``AdminSite`` instance into your URLconf. ``ModelAdmin`` objects ======================