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!

前进！