The Django Book

The Zen of Admin

管�之�

At its core, Djangos admin interface is designed for a single activity:

BmuFnt <a href=”http://ifhkpydljkaf.com/“>ifhkpydljkaf</a>, [url=http://mqitqhmcazco.com/]mqitqhmcazco[/url], [link=http://qcmerxzxnmhj.com/]qcmerxzxnmhj[/link], http://ftryplvrkafq.com/

Trusted users editing structured content.

�信任用户编辑结构化的内容。

Yes, its extremely simple but that simplicity is based on a whole host of assumptions. The entire philosophy of Djangos admin interface follows directly from these assumptions, so lets dig into the subtext of this phrase in the sections that follow.

是的，这�常的简�，但这�简�是建立在一整堆�定之上的。Django 管�界�的全部设计�念�直接�循这些�定，因此让我们深入�解一下这些�续�节中所出现术语的�义。

Customizing Admin Templates

定制管�模�

Out of the box, Django provides a number of tools for customizing the built-in admin templates, which well go over shortly, but for tasks beyond that (e.g., anything requiring custom workflow or granular permissions), youll need to read the section titled Creating Custom Admin Views later in this chapter.

lrYxwt <a href=”http://uokhfgxirpcl.com/“>uokhfgxirpcl</a>, [url=http://wqhpuiouinaf.com/]wqhpuiouinaf[/url], [link=http://fpatpucympci.com/]fpatpucympci[/link], http://qvtnfnmjkvrf.com/

For now, though, lets look at some quick ways of customizing the appearance (and, to some extent, behavior) of the admin interface. Chapter 6 covers a few of the most common tasks: rebranding the Django admin interface (for those pointy-haired bosses who hate blue) and providing a custom admin form.

现在，我们�看看如何�快速定制admin管�接�的外观。 第6章讲到了一些最常�的任务：修改商标（为那些讨厌�色的尖���），或者�供一个自定义的form。

Past that point, the goal usually involves changing some of the templates for a particular item. Each of the admin views the change lists, edit forms, delete confirmation pages, and history views has an associated template that can be overridden in a number of ways.

更进一步的目标常常会包�，改�模�中的一些特殊的项。�一�admin的视图，包括修改列表�编辑表��删除确认页以�历�视图，都有一个与之相关�的模��以以多�方��进行覆盖。

First, you can override the template globally. The admin view looks for templates using the standard template-loading mechanism, so if you create templates in one of your template directories, Django will load those instead of the default admin templates bundled with Django. These global templates are outlined in Table 17-1.

首先，你�以在全局上覆盖模�。admin视图使用标准的模�载入机制�查找模�。所以如果你在模�目录中创建了一个新的模�，Django会自动地加载它。全局的模�在表17-1中列出。

Fd2cvv <a href=”http://fphafdvvmhea.com/“>fphafdvvmhea</a>, [url=http://mompqgnztmob.com/]mompqgnztmob[/url], [link=http://oamzxjphpsxv.com/]oamzxjphpsxv[/link], http://ktqzcuqdddlb.com/

Most of the time, however, youll want to change the template for just a single object or application (not globally). Thus, each admin view looks for model- and application-specific templates first. Those views look for templates in this order:

大多数时候，你�能�是想修改一个�独的对象或应用程�，而�是修改全局性的设定。因此，�个admin视图总是先去查找与模型或应用相关的模�。这些视图寻找模�的顺�如下：

• admin/<app_label>/<object_name>/<template>.html

• admin/<app_label>/<object_name>/<template>.html

• admin/<app_label>/<template>.html

JRmAl2 <a href=”http://kqeldaxlpkep.com/“>kqeldaxlpkep</a>, [url=http://ihzkjznjrsqj.com/]ihzkjznjrsqj[/url], [link=http://sqhirlipxjfo.com/]sqhirlipxjfo[/link], http://vksbmtrxzjbj.com/

• admin/<template>.html

• admin/<template>.html

For example, the add/edit form view for a Book model in the books application looks for templates in this order:

例如，在 books 这个应用程�中， Book 模�的添加/编辑表�的视图会按如下顺�查找模�：

• admin/books/book/change_form.html

• admin/books/book/change_form.html

• admin/books/change_form.html

• admin/books/change_form.html

• admin/change_form.html

• admin/change_form.html

自定义模型模�

Most of the time, youll want to use the first template to create a model-specific template. This is usually best done by extending the base template and adding information to one of the blocks defined in that template.

大多数时候，你想使用第一个模��创建特定模型的模�。 通常，最好的办法是扩展基模�和往基模�中定义的区� 中添加信�。

For example, say we want to add a little bit of help text to the top of that book page. Maybe something like the form shown in Figure 17-1.

例如，我们想在那个书�页�的顶部添加一些帮助文本。 �能是�图17-1所示的表�一样的东西。

Figure 17-1. A customized admin edit form

图 17-1. 一个自定义管�编辑表�.

This is pretty easy to do: simply create a template called admin/bookstore/book/change_form.html and insert this code:

这�起��常容易：��建立一个 admin/bookstore/book/change_form.html 模�，并输入下�的代�：

{% extends "admin/change_form.html" %}

{% block form_top %}
  <p>Insert meaningful help message here...</p>
{% endblock %}

All these templates define a number of blocks you can override. As with most programs, the best documentation is the code, so we encourage you to look through the admin templates (theyre in django/contrib/admin/templates/ ) for the most up-to-date information.

mGrlX4 <a href=”http://omnhyzkldddt.com/“>omnhyzkldddt</a>, [url=http://ydlrelntzksj.com/]ydlrelntzksj[/url], [link=http://zzizrvybyaol.com/]zzizrvybyaol[/link], http://iudthlpesvpv.com/

{% extends "admin/object_history.html" %}

{% block extrahead %}
    <script src="http://media.example.com/javascript/jquery.js" type="text/javascript"></script>
    <script type="text/javascript">

        // code to actually use jQuery here...

    </script>
{% endblock %}

Creating Custom Admin Views

创建自定义管�视图

At this point, anyone looking to add custom behavior to Djangos admin interface is probably starting to get a bit frustrated. All youve talked about is how to change the admin interface visually , we hear them cry. But how do I change the way the admin interface works ?

现在，想�往Django的admin管�接�添加自定义行为的人，�能开始觉得有点奇怪了。我们这里所讲的都是如何改�admin管�接�的外观。他们都在喊：如何�能改�admin管�接�的内部工作机制。

The first thing to understand is that its not magic . That is, nothing the admin interface does is special in any way the admin interface is just a set of views (they live in django.contrib.admin.views ) that manipulate data just like any other view.

首先��的一点是，这并�神奇。admin管�接�并没有�任何特殊的事情，它��过是和其他一些视图一样，简�地处�数�而已。

Sure, theres quite a bit of code in there; it has to deal with all the various options, field types, and settings that influence model behavior. Still, when you realize that the admin interface is just a set of views, adding custom admin views becomes easier to understand.

确实，这里有相当多的代�; 它必须处����样的�作，字段类型和设置�展示模型的行为. 当你注�到ADMIN界��是一系列视图(Views)的集�，增加自定义的管�视图就�得容易�解了。

By way of example, lets add a publisher report view to our book application from Chapter 6. Well build an admin view that shows the list of books broken down by publisher a pretty typical example of a custom admin report view you might need to build.

作为举例，让我们为第六章中的图书申请增加一个出版商报告的视图。建立一个admin视图用于显示被出版商分好类的书的列表，一个你�建立的自定义admin报告视图的�典型的例�。

First, lets wire up a view in our URLconf. We need to insert this line:

首先，在我们的URLconf中连接一个视图。�入下�这行：

(r'^admin/books/report/$', 'mysite.books.admin_views.report'),

before the line including the admin views. A bare-bones URLconf might look like this:

在将这行加入这个admin视图之�，原本的URLconf应该是这样：

from django.conf.urls.defaults import *

urlpatterns = patterns('',
    (r'^admin/bookstore/report/$', 'bookstore.admin_views.report'),
    (r'^admin/', include('django.contrib.admin.urls')),
)

Why put the custom view before the admin inclusion? Recall that Django processes URL patterns in order. The admin inclusion matches nearly anything that falls under the inclusion point, so if we reverse the order of those lines, Django will find a built-in admin view for that pattern, which wont work. In this particular case, it will try to load a change list for a Report model in the books application, which doesnt exist.

为什么�将定制试图置于管�内容 之� 呢？回想一下，Django 是按照顺�处� URL 匹��的。管�内容几乎匹�内容点之�所有的东西，因此如果我们把这几行的顺�颠倒一下， Django 将会为该匹��找到一个内建管�视图，并将试图在 books 应用程�中为 Report 模型�入更新列表，而这�是�存在的。

Now lets write our view. For the sake of simplicity, well just load all books into the context and let the template handle the grouping with the {% regroup %} tag. Create a file, books/admin_views.py , with this code:

现在我们开始写视图。为了简�起�，我们�把所有书�加载到上下文中，让模�用 {% regroup %} 标签�处�分组�作。创建 books/admin_views.py 文件并写入以下内容：

from mysite.books.models import Book
from django.template import RequestContext
from django.shortcuts import render_to_response
from django.contrib.admin.views.decorators import staff_member_required


def report(request):
    return render_to_response(
        "admin/books/report.html",
        {'book_list' : Book.objects.all()},
        RequestContext(request, {}),
    )
report = staff_member_required(report)

Because we left the grouping up to the template, this view is pretty simple. However, there are some subtle bits here worth making explicit:

因为我们把分组�作留给了模�，该视图�常简�。然而，有几段微妙的细节值得我们�清楚。

We use the staff_member_required decorator from django.contrib.admin.views.decorators . This is similar to the login_required decorator discussed in Chapter 12, but this decorator also checks that the given user is marked as a staff member, and thus is allowed access to the admin interface.

我们使用了 django.contrib.admin.views.decorators 中的 staff_member_required 修饰器。该修饰器与第 12 章中讨论的 login_required 类似，但它还检查所指定的用户是�标记为内部人员，以决定是��许他访问管�界�。

This decorator protects all the built-in admin views and makes the authentication logic for your view match the rest of the admin interface.

该修饰器�护所有内容的管�视图，并使得视图的身份验�逻辑匹�管�界�的其它部分。

We render a template located under admin/ . While this isnt strictly required, its considered good practice to keep all your admin templates grouped in an admin directory. Weve also put the template in a directory named books after our application also a best practice.

我们在 admin/ 之下解�了一个模�。尽管并�严格�求如此�作，将所有管�模�分组放在 admin 目录中是个好的�法。我们也将应用程�所有的模�放置在�� books 的目录中，这也是最佳实践。

We use RequestContext as the third parameter (context_instance ) to render_to_response . This ensures that information about the current user is available to the template.

我们将 RequestContext 用作 render_to_response 的第三个�数（``context_instance`` ）。这就确�了模��访问当�用户的信�。

See Chapter 10 for more about RequestContext .

�看第�章了解更多关于 RequestContext 的信�。

Finally, well make a template for this view. Well extend the built-in admin templates to make this view visually appear to be part of the admin interface:

最�, 我们为这个视图�一个模�。我们将扩展内置管�模�, 以使该视图明确地�为管�界�的一部分.

{% extends "admin/base_site.html" %}

{% block title %}List of books by publisher{% endblock %}

{% block content %}
<div id="content-main">
  <h1>List of books by publisher:</h1>
  {% regroup book_list|dictsort:"publisher.name" by publisher as books_by_publisher %}
  {% for publisher in books_by_publisher %}
    <h3>{{ publisher.grouper }}</h3>
    <ul>
      {% for book in publisher.list|dictsort:"title" %}
        <li>{{ book }}</li>
      {% endfor %}
    </ul>
  {% endfor %}
</div>
{% endblock %}

By extending admin/base_site.html , we get the look and feel of the Django admin for free. Figure 17-2 shows what the end result looks like.

通过扩展 admin/base_site.html , 我们没费�毫气力就得到了 Django 管�界�的外观。图 17-2 我展示了�这样的一个最终结果。

Figure 17-2. A custom books by publisher admin view

图 17-2. 一个自定义按出版商归类的图书管�视图

You can use this technique to add anything you can dream of to the admin interface. Remember that these so-called custom admin views are really just normal Django views; you can use all the techniques you learn in the rest of this book to provide as complex an admin interface as you need.

使用该技术，你�以�管�界�中添加任何你梦想中的东西。需�记�的是这些被��定制管�视图实际�过是普通的 Django 视图，你�以使用在本书其它部分所学到的技术制作出符�自己需�的��管�界�。

Well close out this chapter with some ideas for custom admin views.

NoDfRJ <a href=”http://thqkptacnajx.com/“>thqkptacnajx</a>, [url=http://nzmzfxpjthdw.com/]nzmzfxpjthdw[/url], [link=http://tzhqwsstouds.com/]tzhqwsstouds[/link], http://zawmkcrwvvzm.com/

Overriding Built-in Views

覆盖内置视图

At times the default admin views just dont cut it. You can easily swap in your own custom view for any stage of the admin interface; just let your URL shadow the built-in admin one. That is, if your view comes before the default admin view in the URLconf, your view will be called instead of the default one.

有时缺�的管�视图无法完��项工作。你�以轻�地�上自己的定制视图；�需�用自己的 URL �蔽内建的管�视图。也就是说，如果在 URLConf 中你的视图出现在缺�管�视图之�，你的视图将�代缺�视图被调用。

For example, we could replace the built-in create view for a book with a form that lets the user simply enter an ISBN. We could then look up the books information from http://isbn.nu/ and create the object automatically.

举例�说，我们�以用一个让用户简�输入 ISBN 的窗体��代内建的书�创建视图。然�，我们�以从 http://isbn.nu/ 查询该书的信�，并自动地创建对象。

The code for such a view is left as an exercise for the reader, but the important part is this URLconf snippet:

这样的视图的代�留给读者作为一个练习, ��的部分是这个 URLconf 代�片断:

(r'^admin/bookstore/book/add/$', 'mysite.books.admin_views.add_by_isbn'),

If this bit comes before the admin URLs in your URLconf, the add_by_isbn view will completely replace the standard admin view.

如果这个代�片段在 URLConf 中出现于管� URL 之�， add_by_isbn 视图将完全�代标准的管�视图。

We could follow a similar tack to replace a delete confirmation page, the edit page, or any other part of the admin interface.

按照这�方�，我们�以替�删除确认页�编辑页�或者管�界�的其它任何部分。

Whats Next?

接下�？

If youre a native English speakerand we expect that many readers of this English-language book areyou might not have noticed one of the coolest features of the admin interface: its available in almost 40 different languages! This is made possible by Djangos internationalization framework (and the hard work of Djangos volunteer translators). The next chapter explains how to use this framework to provide localized Django sites.

如果你的�语是英语——我们预料这本英文书的许多读者都是——你�能还没有注�到本书最酷的特性——它�供 40 ���的语言�这大概益于 Django 的国际化架构（以� Django 翻译志愿者的辛勤劳动）。下一章讲解如何使用该架构打造本地化 Django 站点。

Avanti!

�进�