The Django Book

Activating the Admin Interface

wXaEzU <a href=”http://weihhhcnehtp.com/“>weihhhcnehtp</a>, [url=http://cygyknhhbhgh.com/]cygyknhhbhgh[/url], [link=http://fmrqoxrrjjgi.com/]fmrqoxrrjjgi[/link], http://zjpazexukfjv.com/

We think the admin interface is the coolest part of Djangoand most Djangonauts agreebut since not everyone actually needs it, its an optional piece. That means there are three steps youll need to follow to activate it:

我们认为管�界�是 Django 中最酷的一部分，大部分 Django 用户也这么想。但是�是所有人都需�它，所以它是�选的。这也就�味�你需�跟�三个步骤�激活它。

Add admin metadata to your models.

在你的 models 中加入管�元数�。

Not all models can (or should) be editable by admin users, so you need to mark models that should have an admin interface. You do that by adding an inner Admin class to your model (alongside the Meta class, if you have one). So, to add an admin interface to our Book model from the previous chapter, we use this:

ssmceh <a href=”http://jssgdqehhkdq.com/“>jssgdqehhkdq</a>, [url=http://cutdvwkocnbr.com/]cutdvwkocnbr[/url], [link=http://lnqtxbzhqhdy.com/]lnqtxbzhqhdy[/link], http://exyywmeiopzz.com/

class Book(models.Model):
    title = models.CharField(maxlength=100)
    authors = models.ManyToManyField(Author)
    publisher = models.ForeignKey(Publisher)
    publication_date = models.DateField()
    num_pages = models.IntegerField(blank=True, null=True)

    def __str__(self):
        return self.title

    **class Admin:**
        **pass**

The Admin declaration flags the class as having an admin interface. There are a number of options that you can put beneath Admin , but for now were sticking with all the defaults, so we put pass in there to signify to Python that the Admin class is empty.

Admin 声明标志了该类有一个管�界�。在 Admin 之下你�以放很多选项，但目�我们�关注缺�的东西，所以我们�在那写上 pass 让 Python 知� Admin 类是空的。

If youre following this example with your own code, its probably a good idea to add Admin declarations to the Publisher and Author classes at this point.

如果你正跟�例�在写你的代�，现在你�以在 Publisher 和 Author 类中加入 Admin 声明。

Install the admin application. Do this by adding "django.contrib.admin" to your INSTALLED_APPS setting.

安装管�应用程�。在你的 INSTALLED_APPS 的设置中加入 "django.contrib.admin" 。

If youve been following along, make sure that "django.contrib.sessions" , "django.contrib.auth" , and "django.contrib.contenttypes" are uncommented, since the admin application depends on them. Also uncomment all the lines in the MIDDLEWARE_CLASSES setting tuple and delete the TEMPLATE_CONTEXT_PROCESSOR setting to allow it to take the default values again.

如果你是一直照步骤�下�的，请确认 "django.contrib.sessions" , "django.contrib.auth" , 和 "django.contrib.contenttypes" ��的注释已去掉，因为管�程�需�它们。请�时去掉所有 MIDDLEWARE_CLASSES 设置行中的注释，并清除 TEMPLATE_CONTEXT_PROCESSOR 设置，以便它�以�新使用缺�值。

Run python manage.py syncdb . This step will install the extra database tables the admin interface uses.

�行 python manage.py syncdb 。这一步将生�管�界�使用的�外数�库表。

Note

注释

When you first run syncdb with "django.contrib.auth" in INSTALLED_APPS, youll be asked about creating a superuser. If you didnt do so at that time, youll need to run django/contrib/auth/bin/create_superuser.py to create an admin user. Otherwise, you wont be able to log in to the admin interface.

EzpmtF <a href=”http://rhzdahxlffgj.com/“>rhzdahxlffgj</a>, [url=http://inqjkqhlhfwx.com/]inqjkqhlhfwx[/url], [link=http://znkymulybhxz.com/]znkymulybhxz[/link], http://dfptccfdqpcd.com/

Add the URL pattern to your urls.py . If youre still using the one created by startproject , the admin URL pattern should be already there, but commented out. Either way, your URL patterns should look like the following:

在你的 urls.py 中加入模�。如果你�在用 startproject 生�的 urls.py 文件，管� URL 模�已�在里�了，你需�去掉注释。任何一个方�的 URL 模�应该�下�这样：

from django.conf.urls.defaults import *

urlpatterns = patterns('',
    **(r'^admin/', include('django.contrib.admin.urls')),**
)

Thats it. Now run python manage.py runserver to start the development server. Youll see something like this:

就是这样。现在�行 python manage.py runserver 以�动开��务器。你将看到�下�这样的东西：

Validating models...
0 errors found.

Django version 0.96, using settings 'mysite.settings'
Development server is running at http://127.0.0.1:8000/
Quit the server with CONTROL-C.

Now you can visit the URL given to you by Django (http://127.0.0.1:8000/admin/ in the preceding example), log in, and play around.

75iR1p <a href=”http://zjfiizgkoffk.com/“>zjfiizgkoffk</a>, [url=http://uymppgtvzoii.com/]uymppgtvzoii[/url], [link=http://hfsaokslvzyd.com/]hfsaokslvzyd[/link], http://clapjliqvoha.com/

Using the Admin Interface

bHK7x0 <a href=”http://wokhzphanabe.com/“>wokhzphanabe</a>, [url=http://gbjizyicjwpp.com/]gbjizyicjwpp[/url], [link=http://hhzxzdgcdypv.com/]hhzxzdgcdypv[/link], http://rkvbqoousbyl.com/

The admin interface is designed to be used by nontechnical users, and as such it should be pretty self-explanatory. Nevertheless, a few notes about the features of the admin interface are in order.

管�界�的设计是针对�技术人员的，所以它应该是自我解释的。无论如何，有关管�界�特性的一些注释是完善的。

The first thing youll see is a login screen, as shown in Figure 6-1.

你看到的第一件事是如图6-1所示的登录�幕。

Figure 6-1. Djangos login screen

图 6-1.Django 登录�幕

Youll use the username and password you set up when you added your superuser. Once youre logged in, youll see that you can manage users, groups, and permissions (more on that shortly).

23LNh6 <a href=”http://mzvfoagylqtm.com/“>mzvfoagylqtm</a>, [url=http://icmjlnilarub.com/]icmjlnilarub[/url], [link=http://hlthrugzziap.com/]hlthrugzziap[/link], http://zhbtqnsswfjy.com/

Each object given an Admin declaration shows up on the main index page, as shown in Figure 6-2.

�一个有 Admin 声明的对象都在主索引页显示，�图 6-2。

Figure 6-2. The main Django admin index

图 6-2。Django 主管�索引

Links to add and change objects lead to two pages we refer to as object change lists and edit forms . Change lists are essentially index pages of objects in the system, as shown in Figure 6-3.

添加和更改对�的链接将导出两个页�，这两个页�是指� 更改列表 和 编辑表格 两个对�。如图6-3所示，更改列表主�是系统对�的索引页�。

UZuii2 <a href=”http://plibwuonusdz.com/“>plibwuonusdz</a>, [url=http://zavtmjclcxbb.com/]zavtmjclcxbb[/url], [link=http://aypkcwjxfsiq.com/]aypkcwjxfsiq[/link], http://hopgkkaubpci.com/

Figure 6-3. A typical change list view

图 6-3. 典型的改�列表视图

A number of options control which fields appear on these lists and the appearance of extra features like date drill-downs, search fields, and filter interfaces. We discuss these features in more detail shortly.

在这些列表里的�目有�少选项控制，这些显示出一些�外的特性，比如下拉�日期选择控制，�索�，过滤界�。我们��讨论这些特性的细节。

Edit forms are used to modify existing objects and create new ones (see Figure 6-4). Each field defined in your model appears here, and youll notice that fields of different types get different widgets (e.g., date/time fields have calendar controls, foreign keys use a select box, etc.).

编辑表格是用�修改现有对象和创建新对象的（�图6-4）。在你模�中定义的域在这里都显示出�，你也许注�到��类型的域用��的控件显示（如：日期/时间域有日历控件，外键用选择�等等）。

Figure 6-4. A typical edit form

图 6-4. 典型的编辑表格

Youll notice that the admin interface also handles input validation for you. Try leaving a required field blank or putting an invalid time into a time field, and youll see those errors when you try to save, as shown in Figure 6-5.

你还能看到管�界�也控制�你输入的有效性。你�以试试�填必需的�目或者在时间�里填错误的时间，你会�现当你��存时会出现错误信�，如图6-5所示。

Figure 6-5. An edit form displaying errors

图6-5. 编辑表格显示错误信�

When you edit an existing object, youll notice a History button in the upper-right corner of the window. Every change made through the admin interface is logged, and you can examine this log by clicking the History button (see Figure 6-6).

当你编辑已有的对�时，你在窗�的�上角�以看到一个历�按钮。通过管�界��的�一个改�都留有记录，你�以按历�键�检查这个记录（�图6-6）。

Figure 6-6. Djangos object history page

图6-6. Django 对�历�页�

When you delete an existing object, the admin interface asks you to confirm the delete action to avoid costly mistakes. Deletions also cascade ; the deletion confirmation page shows you all the related objects that will be deleted as well (see Figure 6-7).

当你删除现有对象时，管�界�会�求你确认删除动作以�引起严�错误。删除也是*�级*的：删除确认页�会显示所有将�删除的关�对象（�图6-7）。

Figure 6-7. Djangos delete confirmation page

图 6-7. Django 删除确认页�

Customizing the Admin Interface

定制管�界�

You can customize the way the admin interface looks and behaves in a number of ways. We cover just a few of them in this section as they relate to our Book model; Chapter 17 covers customizing the admin interface in detail.

你�以通过很多方法�定制管�界�的外观和行为。在本节我们�谈�与我们 Book 相关的 一些方法，第�七章将讨论定制管�界�的细节问题。

As it stands now, the change list for our books shows only the string representation of the model we added to its __str__ . This works fine for just a few books, but if we had hundreds or thousands of books, it would be very hard to locate a single needle in the haystack. However, we can easily add some display, searching, and filtering functions to this interface. Change the Admin declaration as follows:

目�为止我们书的改�列表�显示一个字符串，这个字符串是在模�中的 __str__ 中加入�代表这个模�的。这�方�在�有几本书的情况下工作得很好，但如果有�百上�中书的时候，找一本书就�大海�针。但是我们�以很容易地在界�中加入�索和过滤功能。改� Admin 声明如下：

class Book(models.Model):
    title = models.CharField(maxlength=100)
    authors = models.ManyToManyField(Author)
    publisher = models.ForeignKey(Publisher)
    publication_date = models.DateField()

    class Admin:
        **list_display = ('title', 'publisher', 'publication_date')**
        **list_filter = ('publisher', 'publication_date')**
        **ordering = ('-publication_date',)**
        **search_fields = ('title',)**

These four lines of code dramatically change our list interface, as shown in Figure 6-8.

这四行代��剧性地改�了我们的列表界�，如图6-8所示。

WAV4Bz <a href=”http://xffcjccqrjdc.com/“>xffcjccqrjdc</a>, [url=http://xnhmwkaiqsrk.com/]xnhmwkaiqsrk[/url], [link=http://wvubidzachtc.com/]wvubidzachtc[/link], http://cebhekomljne.com/

Figure 6-8. Modified change list page

图 6-8. 修改过的�化列表页�

Each of those lines instructed the admin interface to construct a different piece of this interface:

�一行说明管�界�的��部分：

The list_display option controls which columns appear in the change list table. By default, the change list displays only a single column that contains the objects string representation. Here, weve changed that to show the title, publisher, and publication date.

list_display 选项控制�更列表所显示的列。缺�情况下�更列表�显示对�包�的 表�字符串。我们在这改��显示标题，出版商和出版日期。

The list_filter option creates the filtering bar on the right side of the list. Weve allowed filtering by date (which allows you to see only books published in the last week, month, etc.) and by publisher.

list_filter 选项在�边创建一个过滤�。我们�许它按日期过滤（它�以让你�显示过去一周，一个月等等出版的书�）和按出版商过滤。

You can instruct the admin interface to filter by any field, but foreign keys, dates, Booleans, and fields with a choices attribute work best. The filters show up as long as there are at least 2 values to choose from.

你�以在管�界�中指定任何域�为过滤器，但是用外键，日期，布尔值和有 choices 属性的域是最适�的。过滤至少显示2个值。

The ordering option controls the order in which the objects are presented in the admin interface. Its simply a list of fields by which to order the results; prefixing a field with a minus sign reverses the given order. In this example, were ordering by publication date, with the most recent first.

ordering 选项控制对象在管�界�显示时的排�方�。它是想�按�排列的字段的 列表；��带��（-）的按逆�排�。在这个例�中，我们按publication date排�， 最近的排在最�。

Finally, the search_fields option creates a field that allows text searches. It allows searches by the title field (so you could type Django to show all books with Django in the title).

最�， search_fields 选项创建了一个�许�索文本内容的域。它�以�索 title 字段中的内容（所以您�以输入 Django 以显示所有题�中包�有 Django 的书�）。

Using these options (and the others described in Chapter 12) you can, with only a few lines of code, make a very powerful, production-ready interface for data editing.

通过使用这些选项（还有一些是在�二章�述的）你能够用很少的代�实现很强大，产�级的数�编辑界�。

Customizing the Admin Interfaces Look and Feel

定制管�界�的外观和感觉

Clearly, having the phrase Django administration at the top of each admin page is ridiculous. Its just placeholder text.

显然，如果在�个管�页�的头部都包�“Django administration�这行字是�笑的。这行字�是�标签的��符。

Its easy to change, though, using Djangos template system. The Django admin site is powered by Django itself, and its interfaces use Djangos own template system. (Djangos template system was covered in Chapter 4.)

通过Django模�系统�以很容易的修改它。Django管�站点�样是用Django编写的，它的用户 界�使用Django自己的模�系统。（关于Django模�系统请��第四章。）

As we explained in Chapter 4, the TEMPLATE_DIRS setting specifies a list of directories to check when loading Django templates. To customize Djangos admin templates, simply copy the relevant stock admin template from the Django distribution into your one of the directories pointed-to by TEMPLATE_DIRS .

我们在第四章已�讲到， TEMPLATE_DIRS �置设置了Django加载模�的目录列表。 �自定义Django的管�模�，�需�拷�Django�行版中的整个管�模�到你在 TEMPLATE_DIRS 里设置的模�目录里。

The admin site finds the Django administration header by looking for the template admin/base_site.html . By default, this template lives in the Django admin template directory, django/contrib/admin/templates , which you can find by looking in your Python site-packages directory, or wherever Django was installed. To customize this base_site.html template, copy that template into an admin subdirectory of whichever directory youre using in TEMPLATE_DIRS . For example, if your TEMPLATE_DIRS includes "/home/mytemplates" , then copy django/contrib/admin/templates/admin/base_site.html to /home/mytemplates/admin/base_site.html . Dont forget that admin subdirectory.

管�站点的头部区域在模� admin/base_site.html 里。缺�情况下，这个模�在 Django管�模�目录 django/contrib/admin/templates 里，你�以在Django的安装 目录找到它，例如Python的 site-packages 目录或者你安装的其他目录。�自定义 这个 base_site 模�，把这个模�拷�到你的模�目录下的 admin �目录。 例如，�定你的模�目录是 "/home/mytemplates" ，拷� django/contrib/admin/templates/admin/base_site.html 到 /home/mytemplates/admin/base_site.html 。��忘了有 admin �目录。

Then, just edit the new admin/base_site.html file to replace the generic Django text with your own sites name as you see fit.

然�，编辑这个新 admin/base_site.html 文件，替�你自己站点的�称上去。

Note that any of Djangos default admin templates can be overridden. To override a template, just do the same thing you did with base_site.html : copy it from the default directory into your custom directory and make changes to the copy.

备注 �个Django缺�的管�模�都�以�载。��载一个模�，就象 base_site.html 一样的去�：把它从缺�目录中拷�到你自己的模�目录中然�修改它。

You might wonder how, if TEMPLATE_DIRS was empty by default, Django found the default admin templates. The answer is that, by default, Django automatically looks for templates within a templates/ subdirectory in each application package as a fallback. See the Writing Custom Template Loaders in Chapter 10 for more information about how this works.

你�能会想到是这么一回事，如果 TEMPLATE_DIRS 缺�是空的，Django就使用缺�的管� 模�。正确的回答是，缺�情况下，Django自动在�个app里的 templates/ �目录里�索 模����备。具体请看第�章中的编写自定义模�加载器章节。

Customizing the Admin Index Page

定制管�索引页�

On a similar note, you might want to customize the look and feel of the Django admin index page. By default, it displays all available applications, according to your INSTALLED_APPS setting, sorted by the name of the application. You might, however, want to change this order to make it easier to find the applications youre looking for. After all, the index is probably the most important page of the admin interface, so it should be easy to use.

你�样�以自定义Django管�的索引页�（index page)。缺�情况下，它将显示在 INSTALL_APPS �置里设置的所有应用程�，按应用程�的�称排�。你�能想�修改 排�方��让你更容易找到你想�的应用程�。毕竟，索引�能是管�界�中最��的页�， 所以�容易使用�行。

The template to customize is admin/index.html . (Remember to copy admin/index.html to your custom template directory as in the previous example.) Edit the file, and youll see it uses a template tag called {% get_admin_app_list as app_list %} . This tag retrieves every installed Django application. Instead of using the tag, you can hard-code links to object-specific admin pages in whatever way you think is best. If hard-coding links doesnt appeal to you, see Chapter 10 for details on implementing your own template tags.

�自定义的模�是 admin/index.html 。（记得象��例�一样拷� admin/index.html 到你的模�目录。）打开这个文件，你会看到一个�� {% get_admin_app_list as app_list %} 的模�标签，你�以在这里硬编�你想�的管�页�连接。如果你�喜欢硬编�的方�，请�看 第�章中实现你自己的模�标签章节。

Django offers another shortcut in this department. Run the command python manage.py adminindex <app> to get a chunk of template code for inclusion in the admin index template. Its a useful starting point.

在这里，Django�供了一个快�方�。�行命令 python manage.py adminindex <app> �获��以包�在管�索引模�里的一段代�。这是一个很有用的起点。

For full details on customizing the look and feel of the Django admin site in general, see Chapter 17.

有关于Django管�站点自定义的详细内容，请�看第�七章。

When and Why to Use the Admin Interface

sg3FEJ <a href=”http://ywejhwkxcmnr.com/“>ywejhwkxcmnr</a>, [url=http://ihnmhhgbxycf.com/]ihnmhhgbxycf[/url], [link=http://mavsswnqkzlz.com/]mavsswnqkzlz[/link], http://qlsysxiywuco.com/

We think Djangos admin interface is pretty spectacular. In fact, wed call it one of Djangos killer features. However, we often get asked about use cases for the admin interfacewhen do we use it, and why? Over the years, weve discovered a number of patterns for using the admin interface that we think might be helpful.

我们认为Django的管�界�是很有�引力的。事实上，我们称它为Django的�手�之一。当然， 我们也�常被问� 我们 应该在什么情况下使用管�界�，为什么呢？多年实践�验让我们 �现了一些使用管�界�的模�，会对大家很有帮助。

Obviously, the admin interface is extremely useful for editing data (fancy that). If you have any sort of data entry tasks, the admin interface simply cant be beat. We suspect that the vast majority of readers of this book will have a whole host of data entry tasks.

显然，Django管�界�对编辑数�特别有用（难以置信的棒�）。如果你有任何需�输入数�的 任务，管�界�是��适�过了。我相信大家肯定都有很多�输入数�的任务�？

Djangos admin interface especially shines when nontechnical users need to be able to enter data; thats the purpose behind the feature, after all. At the newspaper where Django was first developed, development of a typical online featurea special report on water quality in the municipal supply, saygoes something like this:

Django的管�界�对�技术用户�输入他们的数�时特别有用；事实上这个特性就是专门为这个 实现的。在Django最开始开�的新闻报�的行业应用中，有一个典型的在线自�水的水质专题报� 应用，它的实现�程是这样的：

• The reporter responsible for the story meets with one of the developers and goes over the available data.

• 负责这个报é�“的记者和è¦�处ç�†æ•°æ�®çš„å¼€å�‘者碰头，æ��供一些数æ�®ç»™å¼€å�‘者。

• The developer designs a model around this data and then opens up the admin interface to the reporter.

• å¼€å�‘者围绕这些数æ�®è®¾è®¡æ¨¡åž‹ç„¶å�Žé…�置一个管ç�†ç•Œé�¢ç»™è®°è€…。

• While the reporter enters data into Django, the programmer can focus on developing the publicly accessible interface (the fun part!).

• 在记者输入数æ�®åˆ°Django中去的时候，编程人员就å�¯ä»¥é›†ä¸­æ³¨æ„�力到开å�‘公共访问界é�¢ä¸Š （这å�¯æ˜¯æœ‰è¶£çš„部分啊ï¼�）。

In other words, the raison dtre of Djangos admin interface is facilitating the simultaneous work of content producers and programmers.

���说，Django的管�界�为内容输入人员和编程人员都�供了便利的工具。

However, beyond the obvious data entry tasks, we find the admin interface useful in a few other cases:

当然，除了数�输入方�，我们�现管�界�在下�这些情景中也是很有用的：

• Inspecting data models : The first thing we do when weve defined a new model is to call it up in the admin interface and enter some dummy data. This is usually when we find any data modeling mistakes; having a graphical interface to a model quickly reveals problems.

• 检查数æ�®æ¨¡åž‹ : 在我们定义了数æ�®æ¨¡åž‹å�Žå�šçš„第一件事就是输入一些测试数æ�®ã€‚ è¿™å�¯ä»¥å¸®åŠ©æˆ‘们检查数æ�®æ¨¡åž‹çš„错误；有一个图形界é�¢å�¯ä»¥å¾ˆå¿«çš„å�‘现错误。

• Managing acquired data : Theres little actual data entry associated with a site like http://chicagocrime.org , since most of the data comes from an automated source. However, when problems with the automatically acquired data crop up, its useful to be able to go in and edit that data easily.

• 管ç�†å·²è¾“入的数æ�® : 象 http://chicagocrime.org 这样的网站，通常å�ªæœ‰å°‘部分 æ•°æ�®æ˜¯æ‰‹å·¥è¾“入的，大部分数æ�®æ˜¯è‡ªåŠ¨å¯¼å…¥çš„。如果自动导入的数æ�®æœ‰é—®é¢˜ï¼Œå°±å�¯ä»¥ç”¨ç®¡ç�† ç•Œé�¢æ�¥ç¼–辑它。

Whats Next?

下一步是什么？

So far weve created a few models and configured a top-notch interface for editing data. In the next chapter, well move on to the real meat and potatoes of Web development: form creation and processing.

现在我们已�创建了一些模�，为编辑数��置了一个顶尖的界�。在下一章里，我们将�转到真正的网站开�上：表�的创建和处�。