Drupal 8 用户指南

This guide was written mainly for people with minimal knowledge of the Drupal content management
system. The topics will help them become skilled at installing, administering, site building, and/or maintaining
the content of a Drupal-based website. The guide is also aimed at people who already have some experience
with a current or past version of Drupal, and want to expand the range of their skills and knowledge or update
them to the current version.

i
Contents

前言 vii
Copyright . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Audience and Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Reporting Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Conventions of the Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Guiding Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

1 理解 Drupal 1
1.1 概念：Drupal 作为一个内容管理系统 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 概念：模块 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 概念：主题 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4 Concept: Distributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.5 Concept: Types of Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.6 概念：Drupal 项目 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.7 Concept: Drupal Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 规划您的站点 7
2.1 Concept: Regions in a Theme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 Planning Your Site Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3 Concept: Content Entities and Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.4 Concept: Modular Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.5 Planning your Content Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.6 Concept: Editorial Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 安装 15
3.1 概念：服务器要求 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2 Concept: Additional Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.3 Preparing to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.4 Running the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4 基本站点配置 27
4.1 Concept: Administrative Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.2 Editing Basic Site Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.3 Installing a Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.4 Uninstalling Unused Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.5 Configuring User Account Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.6 Configuring the Theme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

5 基本页面管理 43
5.1 Concept: Paths, Aliases, and URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.2 Creating a Content Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.3 Editing a Content Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.4 Editing with the In-Place Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.5 Designating a Front Page for your Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.6 Concept: Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.7 Adding a Page to the Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.8 Changing the Order of Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

iii
CONTENTS

6 内容结构 57
6.1 Adding a Content Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.2 Deleting a Content Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.3 Adding Basic Fields to a Content Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
6.4 Concept: Reference Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.5 Concept: Taxonomy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
6.6 Setting Up a Taxonomy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.7 Adding a Reference Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
6.8 Concept: Forms and Widgets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.9 Changing Content Entry Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.10 Concept: View Modes and Formatters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
6.11 Changing Content Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
6.12 Concept: Image Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
6.13 Setting Up an Image Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
6.14 Concept: Responsive Image Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
6.15 Concept: Text Formats and Editors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
6.16 Configuring Text Formats and Editors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

7 管理用户账号 99
7.1 概念：用户，角色和权限 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
7.2 Concept: The User 1 Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
7.3 Creating a Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
7.4 Creating a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
7.5 Assigning Permissions to a Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
7.6 Changing a User’s Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
7.7 Assigning Authors to Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

8 区块 113
8.1 Concept: Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
8.2 Creating A Custom Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
8.3 Placing a Block in a Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

9 用视图创建列表 119
9.1 Concept: Uses of Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
9.2 概念：视图的组成 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
9.3 Creating a Content List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
9.4 Duplicating a View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
9.5 Adding a Block Display to a View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

10 多语言 135
10.1 Concept: User Interface, Configuration, and Content translation . . . . . . . . . . . . . . . . . . 135
10.2 Adding a Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
10.3 Configuring Content Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
10.4 Translating Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
10.5 Translating Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

11 扩展和自定义网站 145
11.1 Finding Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
11.2 Enabling and Disabling Maintenance Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
11.3 Downloading and Installing a Module from Drupal.org . . . . . . . . . . . . . . . . . . . . . . . . 152
11.4 Finding Themes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
11.5 Downloading and Installing a Theme from Drupal.org . . . . . . . . . . . . . . . . . . . . . . . . 157
11.6 Manually Downloading Module or Theme Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
11.7 Concept: Development Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
11.8 Making a Development Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
11.9 Using Composer and Git to Download Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

iv
CONTENTS

11.10Deploying New Site Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

11.11Synchronizing Configuration Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

12 防止和修复问题 173
12.1 Concept: Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
12.2 Clearing the Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
12.3 Concept: Data Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
12.4 Concept: Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
12.5 Concept: Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

13 安全和维护 179
13.1 Concept: Cron . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
13.2 Configuring Cron Maintenance Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
13.3 Concept: Security and Regular Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
13.4 Keeping Track of Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
13.5 Updating the Core Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
13.6 Updating a Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
13.7 Updating a Theme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

14 结语 189
14.1 Connecting with the Community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
14.2 Getting Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
14.3 Learning More . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

15 词汇表 193

A Appendix 199
A.1 Guide-Wide Attributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Index 201

v
 前言

Copyright
This guide was written by contributors to the Drupal open-source project. It is copyright 2015-2017 by the
individual contributors, and can be used in accordance with the Creative Commons License, Attribution-
ShareAlike 2.0 (CC BY-SA 2.0). Each page in this document (including this one) has an Attributions statement
at the bottom, listing the people who contributed to writing and editing that page. See also Section A.1,
“Guide-Wide Attributions”for guide-wide editing, translating, and project management information.
The CC BY-SA license (very similar to the GPL) allows anyone to copy, modify, and redistribute modifica-
tions of all or part of this work, as long as the following is complied with:
• You provide appropriate credit (see the license for more information).
• You provide a link to the license.

• You indicate whether changes have been made.

• You distribute your work under the same license as this original.
Attributions
This page was adapted and edited by Jennifer Hodgdon, and Jojy Alphonso at Red Crackle, from ”Documen-
tation copyright and licensing”, copyright 2000-2017 by the individual contributors to the Drupal Community
Documentation.
Copyright notice: Copyright 2015-2017 by the individual contributors; see the section called “Copyright”
for details. Licensed under CC BY-SA 2.0.

Audience and Goal

This guide was written mainly for people with minimal knowledge of the Drupal content management system.
The topics will help them become skilled at installing, administering, site building, and/or maintaining the
content of a Drupal-based website. The guide is also aimed at people who already have some experience with a
current or past version of Drupal, and want to expand the range of their skills and knowledge or update them
to the current version.
This guide assumes that you have already decided you want to learn and use Drupal. If you need to learn
more before deciding, see Section 1.1, “概念：Drupal 作为一个内容管理系统”.
Depending on which aspects of Drupal you would like to learn, you will need some background knowledge to
understand this guide: general Internet skills and knowledge are assumed, and the guide concentrates on how
to use the software itself. For instance, the sections about installing Drupal on a web server assume you can
obtain web hosting and figure out how to transfer files to your chosen web host. Similarly, the sections about
content management assume you can log into a website and fill in a web-based form.
After reading this guide, you should be able to:
• Plan the content architecture for a Drupal-based site
• Build the site that you planned

• Manage and administer your site

vii
前言 ORGANIZATION

• Understand documentation and blog posts on topics not covered here, to expand your knowledge and
skills

• Connect with the worldwide Drupal community

Attributions
Written by Jennifer Hodgdon.

Organization
This user guide contains a series of topics, each of which covers either a task (how to do something) or a concept
(background knowledge, terminology, and the like). Concept topics have names starting with Concept:, while
task topics have names containing verbs, like Editing Basic Site Information.
The topics are grouped into chapters in a logical order, with concepts and tasks interleaved so that concepts
are presented before related tasks, and tasks build on each other. To take advantage of this, you are encouraged
to read the entire guide in its presented order, possibly skipping topics that are not of interest or that present
information you already know. Remember to try out the tasks on your own site as you read the guide; most
people learn better by doing rather than reading.
If you prefer, you can also use the index or table of contents to jump straight to a topic that you’d like to
learn about, rather than reading the entire guide. To facilitate this approach, each topic lists the prerequisite
knowledge that you’d need in order to understand it, if any (with links to the topics that present that
knowledge); task topics also list site prerequisites (things that you would need to have configured or created on
your site in order to perform the task). Also, most topics have sections at the end where you can find related
information and/or tasks for expanded understanding, to continue your learning.
You may also want to refer to the 词汇表 section as you read — it gives brief definitions of most of the
terminology used in the guide, with links to topics having more detailed explanations.
Attributions
Written by Jennifer Hodgdon.

Reporting Problems
Goal
Report a problem with this guide, such as:
• Information that is incorrect or does not follow best practices
• Steps that do not work
• Screen shots or text that doesn’t match what you see on the screen

• Unclear writing
• Places where a table or screen shot would help clarify the text
• Failure to define terminology

• Missing knowledge prerequisites or site prerequisites for a topic

• Typographical, spelling, grammar, or formatting errors
• Broken links

viii
前言 CONVENTIONS OF THE GUIDE

Steps
1. Make a note of the topic or topics that contain the problem you have found.

2. Log in to Drupal.org (you will need to create a user account if you do not already have one).
3. Visit the User Guide issues page on Drupal.org.
4. Verify that the problem you found has not already been reported in another issue:

• If there are only a few open issues, scan the Summary column to see if any of their descriptions match
the problem you found. You may also need to read some of the issues to make sure, which you can
do by clicking the links in the Summary column.
• If the open issue list is long, enter either a keyword related to the problem you found or the title of
the topic where the problem occurs in the Search for box, and click Search to reduce the issue list.
Then either scan the summaries or read the issues to see if they match your problem.

5. If you determine that your problem has not already been reported, click Create a new issue, and fill in
the issue report as follows:

Field name Explanation Example value

Title Short summary of the problem Instructions in ”Adding a
you found Content Type” do not work
Category Type of issue being reported Bug report
Version Version of the guide you found 8.x-0.x-dev
the problem in
Issue summary Details of the problem you In the ”Adding a Content
found Type” topic, in step 3, when I
clicked Save, I got the
following error message: …

6. Reread the Title and Issue summary you entered, and verify that the following information is included in
your report:

• A complete description of the problem you found

• The name of the topic or topics where you found the problem
• The language you are reading the guide in (if not English)
• If you read the guide on a website, a link to the page or pages with the problem

7. Click Save to create the issue.

8. Check back on the issue in a few days. If one of the project maintainers has asked for clarification, respond
by adding a comment to the issue.

Attributions
Written by Jennifer Hodgdon.

Conventions of the Guide

Assumptions and prerequisites
This guide has the following assumptions and prerequisites:
• This guide is organized into topics; see the section called “Organization”for details. Many topics include
a Prerequisite knowledge section, which lists other topics whose content knowledge is needed in order to
understand the topic you are reading. Some background knowledge that is not covered in the guide is also
assumed; see the section called “Audience and Goal”for details.

ix
前言 CONVENTIONS OF THE GUIDE

• Many task topics list Site prerequisites, which are tasks that you’ll need to have completed on your site
before you’ll be able to do the task in the topic you are reading.

• The specifics of the site prerequisites relate to the scenario used throughout this guide of building a site
for a farmers market (see the section called “Guiding Scenario”for details). You can adapt the tasks to
your own scenario, but you will also need to remember the changes you made when deciding if your site
satisfies the site prerequisites for a task.

• For all task topics after Section 3.4, “Running the Installer”, there is also an implicit prerequisite: you
must have installed the content management software on your site, and be logged in to a user account
with sufficient permissions to do the task (such as the user account created when you installed your site,
which automatically has full permissions).
• If you read all the topics in order, and perform all of the steps in the task topics as you go (staying logged
in), you should have the background knowledge and site prerequisites in place for each topic as you read
it.

Text conventions
The following conventions are used in the text of this guide:
• The URL example.com means the base URL of your website. See the Navigation section below for more
details on how URLs internal to your site are indicated.
• Text you should see in the user interface of your site is shown in italics, such as: Click Save configuration.
This only applies to text in the user interface that comes from the software, not to text that was entered
in a previous topic. For example, in a topic about editing, you might see this instruction: Click Edit in
the row of the About page (Edit would be in italics, but About would not be, because the About page
was created in a previous topic).
• URLs, file names, and newly-introduced terminology are also shown in italics.

• Text that you should type at a shell command line is shown in monospace type, such as:
drush cr

• Within this guide, the word directory is always used to refer to file directories (which some people prefer
to call folders).

Navigation
To do most of the task topics in this guide, you will need to navigate to one or more pages in the administrative
interface of your site. You might see something like this in the instructions (this will make more sense after you
have the base software installed):
In the Manage administrative menu, navigate to Structure > Taxonomy (admin/structure/taxonomy).
Navigation instructions like this assume that you have the core Toolbar module installed, and this ex-
ample means that in the menu bar at the top of your site, you would need to click Manage to expose the
menu choices, then click Structure, then Taxonomy, and that at the end, you would be on a page with URL
http://example.com/admin/structure/taxonomy (if your site base URL is http://example.com).

Here’s another example:

In the Manage administrative menu, navigate to Configuration > System > Site information (admin/config/system/site-
information).
In this example, after clicking on Manage and Configuration, you would need to find the System section of the
page, and within that, click Site information. After that, you’
d end up on http://example.com/admin/config/system/site-
information.

x
前言 GUIDING SCENARIO

One other note: if you are using the standard administrative core Seven theme, many ”Add” buttons in
the administrative interface are displayed with + signs on them. For instance, on admin/content, the Add new
content button appears as + Add new content. However, this is theme-dependent and is not really part of the
text on the button (for instance, it would not necessarily be read by a screen reader), so in this guide, the
convention is to not mention the + sign on the buttons.

Filling in forms
Many of the task topics in this guide include steps where you will fill out a web form. In most cases, a screen
capture image of the form will be included, along with a table of the values you will need to enter into each form
field. For example, you might see a table that starts out like this, explaining the site information form you would
see if you navigated to Configuration > System > Site information (admin/config/system/site-information):

Field name Explanation Example value

Site name Name of your site Anytown Farmers Market

To use this table, find the field labeled Site name in the form, and enter the name of your site in this field.
An example site name of ”Anytown Farmers Market” is suggested in the table, which relates to the scenario of
building a website for a farmers market that you’ll find all through this guide (see the section called “Guiding
Scenario”for details).
Attributions
Written/edited by Jennifer Hodgdon.

Guiding Scenario
When reading this guide, it is helpful to have a website building project in mind. The following project scenario
provides context and links together the examples in this guide:
You are making a website for a farmers market. The site needs to display information about the location
and hours of the market, and an About page with the history of the market. It also needs to list the vendors.
Vendors should be able to edit their listings (including a logo or photo), and post recipes. Site visitors should
be able to browse recipes, or locate recipes using ingredients that they purchased at the market. Some visitors
to your site speak another language, so the main pages and vendor pages need to be translated.
Attributions
Written/edited by Jennifer Hodgdon.

xi
Chapter 1

理解 Drupal

1.1 概念：Drupal 作为一个内容管理系统

什么是内容管理系统？
内容管理系统（CMS）是一种软件，它允许用户使用智能手机，平板电脑或台式计算机中的 Web 浏览器访问
网站，添加、发布、编辑和删除内容。通常，CMS 软件使用脚本语言编写，运行在安装有数 CMS 或上传的
JavaScript 文件，CSS 文件，图像文件等) 组合起来构建网站的页面。
对于 CMS，运行它的操作系统、编写它的脚本语言、为它存储信息的数据库以及 Web 服务器，构成了运
行它的技术栈。一般使用的组合是 LAMP，即 Linux 操作系统、Apache Web 服务器、MySQL 数据库、和脚
本语言 PHP。

什么是 Drupal?
Drupal 是一个灵活的，基于 LAMP 技术栈的 CMS，它的模块化设计，允许通过安装和卸载模块的方式添加
和移除功能，同时，允许通过安装和卸载主题改变整个网站的视觉感观。我们平时下载的 Dr。下载更多模块和
主题，请访问 Drupal 官网。
Drupal 还可以运行在其他技术栈上：
• 除了 Linux，操作系统还可以是 Windows 或 Mac OS。
• Web 服务器可以用 Nginx 或 IIS，替代 Apache。
• 数据库可以用 PostgreSQL 或 SQLite，替代 MySQL，或者其他兼容 MySQL 的数据库比如 MariaDB 或
Percona。
其他的操作系统，Web 服务器，数据库也可以让它工作。但是，编写它的 PHP 脚本语言，这一点是不变
的。

使用 Drupal 的理由有哪些？
当创建一个网站时，您可以从众多的 CMS 和托管服务中选择，也可以选择开发您自己的 CMS 或者完全不用
CMS。而以下可能是您选择使用 Drupal 的理由：
• 创建一个短小的、简单的静态 HTML 页面并不难，很快，您就可以让一个简单的站点运行起来。而使用
CMS 构建一个网站，开始时通常需要更多时间，但是会带给你一些好处：在线编辑（这对于缺乏经验的
内容维护者很有用），统一管理（对于大型站点使用静态 HTML 是极难维护的），可以构建需要数据库支
持的复杂功能。
• 有的 CMS 仅适合特定用途；比如，您可以使用某些 CMS 和托管服务，来构建博客或俱乐部会员网站。
然而，Drupal 是一个通用的 CMS。如果您正在构建特定用途的网站，您可以选择使用特定用途的 CMS；
但是，如果您的网站会超出那怕一点点预期目的，可能最好选择通用 CMS，而不是专用 CMS。

1
CHAPTER 1. 理解 DRUPAL 1.2. 概念：模块

• 构建自己的 CMS 软件，听起来不错。但是，使用像 Drupal 这类通用 CMS，通常来说，是一个更好的

主意，因为 CMS 的基本功能（比如用户账号和内容管理），其背后，积累的是成千上万开发者的贡献，
并经历了多年的用户测试，Bug 修复和安全加固。
• 某些 CMS 是需要付费的，而且购买它的许可证非常昂贵。也有一些 CMS 声称免费或者提供有免费版
本，但是，其许可证会限制您、不允许您对它进行修改和扩展。您可能更喜欢 Drupal 这样的软，请查看
Section 1.6, “概念：Drupal 项目”。

相关话题
• Section 1.2, “概念：模块”
• Section 1.3, “概念：主题”

• Section 1.4, “Concept: Distributions”

• Section 1.6, “概念：Drupal 项目”

相关资料
• Drupal 概述
• Drupal 官网：FAQ（常见问题）
• Drupal 官网：案例研究

• 维基百科：内容管理系统
• 维基百科：模块化设计

贡献者
编写：Kristof van Tomme @ Pronovix，Jennifer Hodgdon、Michael Lenahan @ erdfisch
翻译：冉强军 @ InterGreat Education Group

1.2 概念：模块
预备知识
Section 1.1, “概念：Drupal 作为一个内容管理系统”

什么是模块？
模块通常包含 PHP、JavaScript 以及 CSS 等文件，用于扩展站点，添加功能特性。安装操作用于启用模块，
卸载操作用于卸载模块。提醒一下，在卸载之前，可能需要移除相关数据和配置。对于每个已安装模块，它会
增加网站页面生成所需时间，所以不需要的模块，最好把它卸载。
Drupal 核心模块，提供的功能有，比如：
• 管理用户账号（User 核心模块）
• 管理基本内容（Node 核心模块）和字段（Field 和 Field UI 核心模块；也有核心模块提供字段类型）
• 管理导航菜单（Menu UI 核心模块）

• 从现有内容制作列表，网格和区块（Views 和 Views UI 核心模块）

您可以从 Drupal 官网：模块下载 下载更多贡献模块，还可以创建自定义模块。

2
CHAPTER 1. 理解 DRUPAL 1.3. 概念：主题

相关话题
• Section 1.3, “概念：主题”
• Section 1.4, “Concept: Distributions”
• Section 4.4, “Uninstalling Unused Modules”
• Section 11.1, “Finding Modules”

• Section 11.3, “Downloading and Installing a Module from Drupal.org”

• Section 13.3, “Concept: Security and Regular Updates”
• Section 13.6, “Updating a Module”

相关资料
Drupal 官网文档：模块开发者指南
贡献者
编写：Jennifer Hodgdon
翻译：冉强军 @ InterGreat Education Group

1.3 概念：主题
预备知识
Section 1.1, “概念：Drupal 作为一个内容管理系统”

什么是主题？
主题是定义站点视觉感观的一系列文件。Drupal 核心和模块决定您的站点显示什么内容（内容包括 HTML 文
本和其他存储在数据库里的数据、上传的图像以及其他资源文件）。主题则决定这些内容的 HTML 标记和 CSS
样式。
Drupal 有提供几个基本主题。这些主题是由社区在过去几年设计和开发的。对于创建第一个网站和熟悉
Drupal 核心如何工作，它们都是不错的选择。
Drupal 是一个成熟的内容管理系统，一般来说，提供（免费或付费）主题的第三方也都值得信赖。
如果第三方提供的主题不能满足您的需求，那么，您需要创建一个自定义主题。一个简单的自定义主题，
可以是单个 CSS 文件，给 Drupal 核心提供的标记添加一些样式。关于如何创建自定义 Drupal 8 主题，请访
问 Drupal 官网文档”Theming Drupal”

相关话题
• Section 11.4, “Finding Themes”
• Section 11.5, “Downloading and Installing a Theme from Drupal.org”
• Section 1.2, “概念：模块”

相关资料
https://www.drupal.org/theme-guide/8 [Drupal 官网文档”Drupal Theming”]
贡献者
编写：John Grubb、Jennifer Hodgdon
翻译：冉强军 @ InterGreat Education Group

3
CHAPTER 1. 理解 DRUPAL 1.4. CONCEPT: DISTRIBUTIONS

1.4 Concept: Distributions

Prerequisite knowledge
• Section 1.1, “概念：Drupal 作为一个内容管理系统”
• Section 1.2, “概念：模块”

• Section 1.3, “概念：主题”

What are Distributions?

Distributions provide site features and functions for a specific type of site as a single download containing the
core software, contributed modules, themes, and pre-defined configuration. A distribution makes it possible to
set up a complex, use-specific site in fewer steps than installing and configuring elements individually.
There are two main types of distributions:
Full-featured Distributions A full-featured distribution is a project that provides a complete solution to
set up a site for a specialized purpose such as academic, business, government, nonprofit, publishing,
social, etc. For example, you could use an existing distribution for farmers markets to build your own
website, or you could share your set-up for the farmers market site as a distribution for others to use.
Other Distributions Distributions can also be quick-start tools that developers and site builders can use
as a starting point.

Related topics
Section 14.1, “Connecting with the Community”

Additional resources
Drupal.org Drupal Distribution Downloads
Attributions
Adapted and edited by Diána Lakatos and Antje Lorch, from ”Distributions” and ”Download & Extend —
Distributions” copyright 2000-2017 by the individual contributors to the Drupal Community Documentation.

1.5 Concept: Types of Data

What are the types of data?
The data and information on your site is divided up into four types, which are edited, translated, and stored
differently. These four types are:
Content Information (text, images, etc.) meant to be displayed to site visitors. This type of information
tends to be relatively permanent, but can normally be edited.
Configuration Information about your site that is not content, but is also relatively permanent, and is used
to define how your site behaves or is displayed. It is sometimes also displayed to site visitors, but tends
to be smaller pieces of text (like field labels, the name of your site, etc.) rather than larger chunks that
you’d normally think of as Content.
State Information of a temporary nature about the current state of your site, such as the time when cron
jobs were last run.

Session Information about individual site visitors’ interactions with the site, such as whether they are logged
in and their cookies. This is technically a subtype of State information, since it is also temporary.

4
CHAPTER 1. 理解 DRUPAL 1.6. 概念：DRUPAL 项目

Related topics
• Section 2.3, “Concept: Content Entities and Fields”
• Section 13.1, “Concept: Cron”
• Section 7.1, “概念：用户，角色和权限”
• Section 10.1, “Concept: User Interface, Configuration, and Content translation”

Attributions
Adapted by Jennifer Hodgdon from ”Overview of Configuration (vs. other types of information)”, copyright
2000-2017 by the individual contributors to the Drupal Community Documentation

1.6 概念：Drupal 项目
预备知识
Section 1.1, “概念：Drupal 作为一个内容管理系统”

什么是自由及开放源代码软件？
自由和开源软件（FOSS）是由一种由社区的人共同开发，以非商业许可进行发布，其源代码（组成软件的程
序文件）可以免费获取的软件。关于 Drupal 使用的非商业许可证的更多信息，请查看 Section 1.7, “Concept:
Drupal Licensing”。

什么是 Drupal 项目？

Drupal 项目是一个 FOSS 项目，它的目的是开发内容管理核心软件，以及模块，主题、翻译、文档和发行版。
为 Drupal 项目贡献时间和金钱的人来自世界各地，因为这个共同目的相聚在这个多元化的社区。
社区包括许许多多小的群组，他们执行许多不同的任务，比如开发一小块 Drupal 相关的软件、写作文档、
维护 Drupal 软件的安全、翻译 Drupal 软件、以及因为使用 Drupal 的一些特定目的，聚集在一个特定地理区
域亲自见面。
有关如何与世界范围内的社区建立连接和进行沟通，请查看 Section 14.1, “Connecting with the Commu-
nity”和 Section 14.2, “Getting Support”。

什么是 Drupal 协会？

Drupal 协会 是一个致力于 Drupal 项目和社区的非营利性组织。它的主要功能有：
• 负责世界范围内的大型 Drupal 会议
• 维护 Drupal.org 及其服务器
• 推广 Drupal 作为一个网络平台
• 支持 Drupal 教育和培训
• 为 Drupal 社区提供资助以支持其使命
• 为这些目的筹集资金

相关话题
• Section 1.7, “Concept: Drupal Licensing”
• Section 13.3, “Concept: Security and Regular Updates”
• Section 14.1, “Connecting with the Community”
• Section 14.2, “Getting Support”

5
CHAPTER 1. 理解 DRUPAL 1.7. CONCEPT: DRUPAL LICENSING

相关资料
• Drupal 项目管理
• Drupal 行为准则

贡献者
写作：Jennifer Hodgdon
翻译：冉强军 @ InterGreat Education Group

1.7 Concept: Drupal Licensing

Prerequisite knowledge
Section 1.1, “概念：Drupal 作为一个内容管理系统”

What is Drupal Licensing?

Drupal and all contributed files hosted on Drupal.org are licensed under the GNU General Public License (GPL),
version 2 or later. That means you are free to download, reuse, modify, and distribute any files that are part of a
project on Drupal.org under the terms of GPL version 2 or 3. You can also run the core software in combination
with any code with any license that is compatible with version 2 or 3.
Drupal contributors should follow these guidelines:
• All files (PHP, JavaScript, images, Flash, etc.) that are part of a project on Drupal.org have to be under
GPL version 2 or later.
• All Drupal contributors retain copyright on their code, but agree to release it under the same license as
Drupal.
• Drupal modules and themes are a derivative work of Drupal. If you distribute them, you must do so under
the terms of GPL version 2 or later.
• All content on Drupal.org itself is copyrighted by its original contributors, and is licensed under the
Creative Commons Attribution-ShareAlike license 2.0.

• Sample code on Drupal.org is also available under GPL version 2 or later.

Related topics
Section 14.1, “Connecting with the Community”

Additional resources
• Drupal.org page on ”Licensing”

• ”Drupal 8 LICENSE.txt” page on api.drupal.org

• GNU General Public License, version 2
• GNU General Public License, version 3

• Creative Commons Attribution-ShareAlike license 2.0.

• ”Legal Group” on groups.drupal.org

Attributions
Adapted by Diána Lakatos at Pronovix from ”Licensing” copyright 2000-2017 by the individual contributors
to the Drupal Community Documentation.

6
Chapter 2

规划您的站点

2.1 Concept: Regions in a Theme

Prerequisite knowledge
Section 1.3, “概念：主题”

What is a region?
Besides its primary content, a web page contains other content such as site branding (site name, slogan, and
logo), navigation aids (menus, links, and icons), formatted text, and images. Each theme provides a set of
named regions, such as Header, Content, and Sidebar, where site builders may choose to place their content.
The available regions depend on the theme design. Only the Content region, which contains the primary
content, is required; others are optional. The core Bartik theme provides the eighteen regions highlighted in
the following image.

7
CHAPTER 2. 规划您的站点 2.2. PLANNING YOUR SITE LAYOUT

Related topics
• Section 8.1, “Concept: Blocks”
• Section 2.3, “Concept: Content Entities and Fields”
• Section 8.3, “Placing a Block in a Region”

Additional resources
• Drupal.org community documentation page ”Assigning content to regions”

Attributions
Written and edited by John MacDonald, and Michael Lenahan at erdfisch.

2.2 Planning Your Site Layout

Goal
Plan the navigation and layout of the site, for both mobile and desktop browsers.

Prerequisite knowledge
• Section 1.3, “概念：主题”
• Section 2.1, “Concept: Regions in a Theme”
• the section called “Guiding Scenario”

Steps
It is a good idea to plan the site layout before you start building the site and writing content; however, your
plan may need to be revised either before you start implementing it or after you have some of the site built
with draft content in place, based on budgetary concerns or stakeholder feedback.
1. Make a list of the information that your site should present to visitors. In the farmers market scenario,
this might include:

• Location of the market, with directions and a map

• Hours and days the market is open
• History of the market
• List of vendors
• Details about each vendor
• Searchable list of recipes
• Details about each recipe
• List of the most recently added recipes

2. Decide which information should be on which pages or types of pages on the site:
Information that should be on all pages Address, hours, and recently-added recipes list
Vendor details pages Information about each vendor on its own page
Recipe details pages Details of each recipe on its own page
Home page Location, map, directions, and hours
About page History of the market
Vendors list page List of vendors, with links to vendor detail pages

8
CHAPTER 2. 规划您的站点 2.3. CONCEPT: CONTENT ENTITIES AND …

Recipe list page Searchable list of recipes, with links to recipe detail pages

3. Decide which information is the most important on each page. Site visitors using mobile phones or other
small browsers will often only see the content that is presented first, and they may not scroll down to see
all of the information.
4. Decide which of these pages should appear in the main site navigation. For instance, the main navigation
might consist of the Home, About, Vendors, and Recipes pages.

5. Make a rough design sketch for each page, showing how it would look when viewed on a small screen such
as a phone, as well as on a larger screen such as a desktop browser. Considering that most site visitors
will be using smaller browsers, it is a good idea to start with the phone-size layout, to make sure that
these visitors will be able to find the information they need without too much scrolling.
In making these page layout plans, you might find that you need to revise your plan for which information
should be on which pages. For example, you might decide that the address, hours, and recently-added
recipes list would all fit well in the right sidebar area of all pages, when the site is viewed on desktop-sized
browsers. On the other hand, you might decide that for mobile browsers, you would instead put the
address and hours in a short format at the top of each page, but only display the recent recipe list at the
bottom of the home page.

Expand your understanding

Section 2.5, “Planning your Content Structure”
Attributions
Written by Jennifer Hodgdon.

2.3 Concept: Content Entities and Fields

Prerequisite knowledge
• Section 1.5, “Concept: Types of Data”

• Section 1.2, “概念：模块”

What is a content entity?

A content entity (or more commonly, entity) is an item of content data, which can consist of text, HTML
markup, images, attached files, and other data that is intended to be displayed to site visitors. Content entities
can be defined by the core software or by modules.
Content entities are grouped into entity types, which have different purposes and are displayed in very
different ways on the site. Most entity types are also divided into entity sub-types, which are divisions within
an entity type to allow for smaller variations in how the entities are used and displayed. Here is a table of some
common content entity types:

Entity type Entity sub-type Defining Module Main uses

Content item Content type Node module Content intended to be
the main page area for
pages on the site
Example: In the farmers market site example, you might have content types
for basic pages, vendor pages, and recipe pages.
Comment Comment type Comment module Commentary added to
content entities
(typically to Content
item entities)
Example: On a blog site, blog posts might have comments. They are not
needed in the farmers market site example.

9
CHAPTER 2. 规划您的站点 2.3. CONCEPT: CONTENT ENTITIES AND …

Entity type Entity sub-type Defining Module Main uses

User profile (none) User module Data related to a person
with a user account
(login access) on the site
Example: Every site has at least basic user profiles with user names and
email addresses; social networking sites may have more complex user profiles
with more information.
Custom block Block type Custom Block module Text and images in
smaller chunks, often
displayed in the site
header, footer, or
sidebar
Example: In the farmers market site example, you might put the hours and
location in a sidebar block.
Taxonomy term Vocabulary Taxonomy module Used to classify other
types of content
Example: In the farmers market site example, you might classify Recipe
content with an Ingredients taxonomy vocabulary, with taxonomy terms like
Carrots and Tomatoes. In a blogging site, blog posts might be classified using
a Tags vocabulary, and perhaps also a Categories vocabulary.
File (none) File module An image or attachment
file that is tracked and
managed by the site,
often attached to other
types of content
Example: In the farmers market site example, both Recipe and Vendor pages
might have image attachments, which would (behind the scenes) be managed
as File entities by the site.
Contact form Form type Contact module A form that lets site
visitors contact site
owners
Example: A contact form is needed in the farmers market site example.

What is a field?
Within entity items, the data is stored in individual fields, each of which holds one type of data, such as
formatted or plain text, images or other files, or dates. Field types can be defined by the core software or by
modules.
Fields can be added by an administrator on entity sub-types, so that all entity items of a given entity sub-
type have the same collection of fields available. For example, the Vendor content type in the farmers market
example might have fields for the vendor name, a logo image, website URL, and description, whereas the Basic
page content type might only have fields for the title and page body. When you create or edit entity items, you
are specifying the values for the fields on the entity item.

Related topics
• Section 2.5, “Planning your Content Structure”

• Section 5.2, “Creating a Content Item”

• Section 6.1, “Adding a Content Type”
• Section 6.5, “Concept: Taxonomy”

• Section 7.1, “概念：用户，角色和权限”

• Section 8.1, “Concept: Blocks”

10
CHAPTER 2. 规划您的站点 2.4. CONCEPT: MODULAR CONTENT

Attributions
Written and edited by Jennifer Hodgdon and Grant Dunham.

2.4 Concept: Modular Content

Prerequisite knowledge
• Section 2.3, “Concept: Content Entities and Fields”
• Section 2.2, “Planning Your Site Layout”

What is modular content?

Given that the content of your site is stored in a database, it is desirable to make the content modular, meaning
that certain pages on your site, rather than being edited as a whole page, are instead generated automatically
from other content items. For instance, in the farmers market site scenario, you might create individual content
items for recipes. If the recipe content items have a field that keeps track of ingredients, then your site could
include a composite page that would list recipes, and allow visitors to search for a recipe that contained some
particular ingredient they had bought at the market.
Smaller sections of pages can also be generated as composites. For instance, recipe content items could have
a field that keeps track of which vendor submitted the recipe (see Section 6.4, “Concept: Reference Fields”),
with the vendor details edited in separate vendor content items. This would allow you to do the following on
your site:
• On each Recipe page, there could be an area that displays some information about the vendor that
submitted the recipe, such as their name and market stall number.
• Each vendor page could have a section that lists the recipes they have submitted.
The key idea is that each piece of information is only edited in one place. When vendor information is
updated, all recipe pages that display that vendor information are automatically updated; when a recipe is
submitted by a vendor, it is automatically displayed on the vendor page. The core Views module is the usual
way to use modular content to create composite pages and page sections; see Section 9.1, “Concept: Uses of
Views”for more information. Also, view modes are useful for defining different ways to display each content
item; see Section 6.10, “Concept: View Modes and Formatters”for more information.

Related topics
• Section 2.5, “Planning your Content Structure”
• Section 6.1, “Adding a Content Type”
• Section 6.3, “Adding Basic Fields to a Content Type”
• Section 6.4, “Concept: Reference Fields”
• Section 6.10, “Concept: View Modes and Formatters”
• Section 9.1, “Concept: Uses of Views”

Attributions
Written by Jennifer Hodgdon.

2.5 Planning your Content Structure

Goal
Make a plan for the content structure of the site (which type and subtype of entity to use for which content),
and which pages will contain listings of content.

11
CHAPTER 2. 规划您的站点 2.5. PLANNING YOUR CONTENT STRUCTURE

Prerequisite knowledge
• Section 2.3, “Concept: Content Entities and Fields”

• Section 2.4, “Concept: Modular Content”

• the section called “Guiding Scenario”

Steps
1. Brainstorm about what content your site needs to contain, which could include content that visitors would
be looking for, as well as content that you want to show to visitors. The result could be the description
in the section called “Guiding Scenario”.
2. For each identified piece of content, decide which content entity type would be the best fit. In doing this,
you’ll need to consider where and how the content will be used and edited on the site. For example, in
the farmers market site scenario, you might want to display the hours and location of the farmers market
on the sidebar of every page. For that content, a single custom block makes sense. As another example,
you might decide that pages displaying information about each vendor should be content items managed
by the core Node module, because you want vendors to be able to edit their own listings. The core Node
module permission system lets you do this easily.
These decisions do not necessarily always have only one right answer; for instance, you could decide that
vendor pages should be user profiles instead of content items, but if you did that the content would be
tied to a specific user account, and it would not be as easy to later change the ownership of a vendor page
to a different user account.
3. Within each content entity type you identified, decide what division into entity sub-types would make
sense. For example, in the farmers market site example, you would probably decide that under the Content
item entity type, there should be one content type for basic pages (Home and About), one for vendor
pages, and one for recipe pages.
4. For each entity sub-type you decided on, decide what fields are needed. For instance, the Vendor content
type might need fields for the vendor name, web page URL, image, and description.

5. Decide on what entity listings are needed, which could be entire pages or smaller areas on the page. For
each listing, you’ll need to determine what entity items should be listed. Then you’ll need to decide
in what order and with what filtering options they should be displayed; for example, you might want to
give the site visitor the option to search by keyword, to filter the list down to a subset, or to sort the list.
You’ll also need to decide what information from the entity items should be shown, which might result
in adding to the list of fields you determined in the previous step. The farmers market site, for example,
needs to have a Recipes listing page that lists content items of type Recipe, with the ability to filter by
ingredients, so that means that the Recipe content type needs an Ingredients field.
6. For each identified field on each entity subtype, identify what type of data it should contain (such as plain
text, formatted text, a date, an image file, etc.), and how many values should be allowed. Most fields are
single-valued, but for example, a Recipe should allow for multiple values in its Ingredients field.

7. Consider which fields would be best as references to taxonomy term entities: fields whose values should
be chosen from a list of allowed values. Allowed values that are expected to change and grow over time,
are good candidates. An example is the Ingredients field for the Recipe content type.
8. Consider which fields should reference other content entities. An example is that since vendors will be
submitting recipes, a field will be needed on the Recipe content type that references the Vendor content
item for the vendor who submitted the recipe.

Here’s an example of the resulting content structure for the farmers market scenario example site:

12
CHAPTER 2. 规划您的站点 2.6. CONCEPT: EDITORIAL WORKFLOW

Entity type Entity sub-type Examples Fields

Content item Basic page Home page, about page Title, page body
Content item Vendor A page for each vendor Vendor name, page
at the market body, image, URL
Content item Recipe A page for each Recipe name, page
submitted recipe body, image, reference
to Vendor who
submitted it,
Ingredients taxonomy
Custom block (generic) Copyright notice for No special fields
footer, Hours and
location for sidebar
Taxonomy term Ingredients Carrots, tomatoes, and No special fields
other recipe ingredients
Contact form (generic) Generic contact form Name, email, subject,
message
User profile (none) Will not be displayed No special fields
on site

And here are the listings the site needs:

Page or page area Entity type and Filter/sort/pagination Fields displayed

sub-type
Vendors page Vendor content items All vendors, Image, vendor name,
alphabetical, paged trimmed body
Recipes page Recipe content items Filter by ingredients, Image, recipe name
alphabetical, paged
Recent recipes sidebar Recipe content items List 5 most recent Image, recipe name

Expand your understanding

• Section 6.1, “Adding a Content Type”
• Section 6.3, “Adding Basic Fields to a Content Type”
• Section 6.6, “Setting Up a Taxonomy”

Related concepts
Section 6.5, “Concept: Taxonomy”
Attributions
Written and edited by Jennifer Hodgdon and Grant Dunham.

2.6 Concept: Editorial Workflow

Prerequisite knowledge
Section 1.1, “概念：Drupal 作为一个内容管理系统”

What is an Editorial Workflow?

An Editorial Workflow is the process organizations follow to create, review, edit and publish content.
Depending on the size and processes of the organization, multiple people in different roles can be part of
the process. For example, content creators collect information and write content, editors review, edit, ask for
changes, and publish the content once it’s considered ready to be shared with the audience.

13
CHAPTER 2. 规划您的站点 2.6. CONCEPT: EDITORIAL WORKFLOW

In your site, content types can have either a Published or an Unpublished flag to track their workflow states,
that you can set for each content item when saving:

• Published content items are visible to all visitors of the site.

• Unpublished content items are not visible to the visitors of the site, but can be seen by authenticated
users who have the permissions to view unpublished versions of specific content items.
Most content entity types support revision tracking, if it is enabled by an administrator for the entity sub-
type. If you have revision tracking enabled, the software will store old versions of the content each time it’
s revised, and add notes about what is changed. This allows you to look at the history and revert to older
versions.
Using the Unpublished flag and Revisions, you can build an editorial workflow that lets content creators
and editors work on the live site without displaying the content to visitors. When the content is ready to be
published, all they need to do is save it as Published.

Related topics
• Section 5.2, “Creating a Content Item”

• Section 5.3, “Editing a Content Item”

Additional resources
Talking about online content, organizations would also want to consider post-publication phases of the editorial
workflow: content teams might need to update already published content. Some organizations might need a
more complex workflow with the options to configure which content type goes through the workflow process,
set up user roles and permissions, set different workflow states (for example draft, needs review, published).
For more complex workflows, you can add install or more modules from the contributed Workbench Suite
module to your site.
Attributions
Written and edited by Diána Lakatos at Pronovix, and Grant Dunham.

14
Chapter 3

安装

3.1 概念：服务器要求
运行核心软件的要求有哪些？
磁盘空间
最低安装需 15MB 磁盘空间。当网站安装大量的贡献模块和主题时需要 60MB 磁盘空间。谨记，你需要更多空
间用于数据库、用户上传的文件、媒体文件、备份文件及其他文件。

Web 服务器

Apache (推荐) Apache 是最常用的 Web 服务器。核心软件能在运行 Apache 2.x 的 UNIX/Linux、OSX、

或 Windows 系统中工作，并确保 Apache mod_rewrite 模块已安装并已开启。Apache VirtualHost 配置
必须包含指令 AllowOverride All ，以允许使用 .htaccess 文件。

Nginx Nginx 也是常用的 Web 服务器，Nginx 服务器侧重高并发性，高性能和低内存占用。核心软件能在运

行 Nginx 1.1 或其更高版本的 UNIX/Linux、OSX、或 Windows 系统中工作。ngx_http_rewrite_module
必须安装并启用。
Hiawatha Hiawatha 是一个注重安全性的 Web 服务器。同时，Hiawatha 一直致力于易用性和轻量性。独立
研究人员进行的研究表明，Hiawatha 在正常条件下提供了与其他 Web 服务器相当的性能，在受到网络
入侵时，能提供更好的性能。必须安装并配置 URL Toolkit 才能重写 URL。
微软 IIS 微软 IIS 是一个 Web 服务器，它有一系列在微软 Windows 系统下使用的功能扩展模块。如果 PHP
配置正确的话，核心软件可以在 IIS 5、IIS 6 及 IIS 7 服务器中运行。由于简洁链接是必需的，你需要用
到第三方产品。对于 IIS 7 来说，你可以使用微软的 URL 重写模块或者第三方的解决方案。

数据库
可从下列数据库中任意选中一个：

• MySQL - 5.5.3 (MariaDB 5.5.20, Percona 5.5.8) 或兼容 InnoDB 主存储引擎的更高版本

• PostgreSQL - 9.1.2 或更高版本
• SQLite - 3.4.2 或更高版本

PHP
PHP 5.5.9 或更高版本

15
CHAPTER 3. 安装 3.2. CONCEPT: ADDITIONAL TOOLS

相关资料
Drupal 官网文档：系统要求
贡献者
编写：Karl Kedrovsky 和 Brian Emery
翻译：周宇，冉强军 @ InterGreat Education Group

3.2 Concept: Additional Tools

What tools are available for site builders?
There are several additional tools available that help you create sites faster, more accurately and with less effort.
Drush See below for more about Drush.
Git Git is a version control system you can use to track changes made to files within your entire site, or files
relating only to the module or theme that you are using. Git makes it possible to try out changes, and if
necessary, revert to a previous version. It can be used as well to track changes in the configuration files
and synchronize the configuration of different sites. Git has become the standard for web development
projects.
Composer See below for more about Composer.
Devel The contributed Devel module helps with development tasks such as debugging and inspecting code,
analyzing database queries, and generating dummy content.

What is special about Drush?

Drush is a command-line tool for building and maintaining sites, providing an alternative to using the ad-
ministrative interface for many operations. Many site builders and maintainers prefer to use Drush whenever
possible, and consider the time spent installing and learning to use Drush to be a good investment. Reasons to
consider using Drush:
• Drush provides a large number of commands for tasks such as installing the base software, modules, and
themes; updating software; performing database operations, including copying and querying; resetting
passwords; and clearing the cache. Some contributed modules and themes also define Drush commands.
• Doing administrative tasks using Drush is typically faster and less tedious than performing the same tasks
through the administrative interface.
• Since Drush is a command-line interface, you can write scripts that combine Drush commands and other
commands on the server, to automate more complicated tasks.
• Drush provides additional functionality not available via the administrative interface; for example, running
database queries.
If you want to use Drush, you will need to have command-line terminal access to the server where your
website will be hosted, and you will need to have a compatible version of the Drush tool installed on that server.
Check the Drush website for installation instructions and version compatibility. There is also documentation
on the available Drush commands on that site.

What is Composer used for?

Composer is a tool for managing PHP dependencies, where the developer specifies what version of each external
library is needed, and Composer manages the process of downloading and installing the libraries.
The core software is a primary user of Composer, because it makes use of several externally-developed
software libraries, which must be downloaded and installed in order for the core software to work. When
you install the core software, you either need to download an archive that contains compatible versions of the
external libraries, or you need to run Composer to download the external libraries after the initial download.

16
CHAPTER 3. 安装 3.3. PREPARING TO INSTALL

Some contributed modules also make use of externally-developed software libraries; for example, a Facebook
integration module might require Facebook’s integration library to be installed for the module to work, and a
geographical module might make use of a standard library of geographical functions. To install a module with
external dependencies, you will need to run Composer.

What tools are available for module and theme developers?

In addition to the site builder tools mentioned above, the following tools are useful for module and theme
developers.
Drupal Console Drupal Console is a command-line tool that generates boilerplate code and interacts with
a Drupal site. It can generate, for example, block or form code, install modules and themes, and create
dummy content. Drupal Console makes use of the Symfony Console.

Coder Coder is a command-line tool that checks if your modules and themes comply with coding standards
and other best practices. It can also fix coding standard violations.
Firebug Firebug is a Firefox plugin that allows viewing, editing, debugging, and monitoring CSS, HTML,
and JavaScript in a separate browser window. The contributed Drupal for Firebug module displays Drupal
debugging and SQL query information in the Firebug window.

Related topics
Section 11.9, “Using Composer and Git to Download Files”

Additional resources
• Drupal.org community documentation page ”Development tools”

• Drupal.org community documentation page ”Using Composer with Drupal”

Attributions
Written and edited by Boris Doesborg and Jennifer Hodgdon.

3.3 Preparing to Install

Goal
Choose an appropriate way to install the core software, and handle any required prerequisites.

Prerequisite knowledge
• Section 3.1, “概念：服务器要求”

• Section 3.2, “Concept: Additional Tools”

Site prerequisites
If you want to use Drush to install the core software, Drush must be installed. See Section 3.2, “Concept:
Additional Tools”.

17
CHAPTER 3. 安装 3.3. PREPARING TO INSTALL

Steps
1. Choose a method for installing the core software.

Try a free online demo Use an online provider to get a demo installation of the core software in 20
minutes or less. See the Drupal.org page ”Try Drupal”.
Use a one-click installer from your hosting provider If you choose to install the core software at
your hosting provider, your hosting provider may have specific documentation and/or a one-click
install that you can use. See Drupal.org’s list of hosting providers that support Drupal.
Use Drush You will need to have Drush installed and command-line access to the site. See Section 3.2,
“Concept: Additional Tools”.
Use the web installer You will need space on a local or hosted web server to install the core software
manually.
Use a pre-configured environment Use a pre-configured environment or virtual machine that con-
tains Drupal and all the required supporting software to install Drupal locally. See the section for
your operating system under Drupal.org’s Local server setup guide for possible options.
2. If you are installing using Drush or the web installer, set up a URL and hosting for your site, either at
an external hosting provider or on your own computer. Verify that the hosting is working by putting a
simple HTML file in the web root directory of the hosting, and visiting the URL for your site.

3. If you are installing using Drush or the web installer, create a database, along with a database user account
with full access.
4. If you are installing using Drush, type the following at the Drush command line, where example is the
name of the directory that the core software will be downloaded to, and DB_NAME, DB_USER and
DB_PASS are your database’s credentials:
drush dl drupal --drupal -project - rename = example
cd example
drush site - install standard --db -url=' mysql :// DB_USER : DB_PASS@localhost /DB_NAME ' ←-
--site - name= example

5. If you are installing using the web installer, upload the core software files manually. To do this using
Git and/or Composer, see Section 11.9, “Using Composer and Git to Download Files”; to do this by
downloading a zipped archive:

a. Go to https://www.drupal.org and click Download & Extend on the top-level menu.

b. Click the Download Drupal button (of the appropriate version) to be taken to the Downloads page.

18
CHAPTER 3. 安装 3.3. PREPARING TO INSTALL

c. Click the version you wish to download under Recommended releases.

d. Download the tar.gz or zip file to your local machine.

e. Upload the downloaded file to your hosting account. Log in to the control panel and navigate to the
HTML directory. Save the file there.
f. Uncompress the tar.gz or zip file, which will create a new directory. If you do not have terminal
access, or your hosting server is not running Linux, your hosting control panel’s file manager should
provide a way to extract the files. If you have terminal access to your hosting server (running Linux),
you can use a command like:
tar -xzf drupal -8.3.2. tar.gz

g. Delete the compressed file from the server, unless your unpacking method already deleted it.
h. Rename the directory or reconfigure your web hosting, so that the directory name matches the
directory your web hosting is configured to use for your site.

Expand your understanding

Run the installer if you chose web installer to install the core software. See Section 3.4,“Running the Installer”
.

19
CHAPTER 3. 安装 3.4. RUNNING THE INSTALLER

Additional resources
Drush
Attributions
Written and edited by Drew Gorton, Michael Lenahan at erdfisch, Jennifer Hodgdon, and Jojy Alphonso at
Red Crackle.

3.4 Running the Installer

Goal
Install the core software and create the admin account by running the included installer.

Prerequisite knowledge
Section 3.1, “概念：服务器要求”

Site prerequisites
Section 3.3, “Preparing to Install”

Steps
1. If you are using a 1-click install from a hosting provider or demo site, you will most likely see some or
all of the following screens as part of the installation process. If you uploaded the core files manually, to
start the installer, open a browser and visit the URL that you set up for your hosting.
2. Select a language on the first page of the installer; for example, English. You could optionally choose
from any of the other listed languages. The language files for the chosen language will be downloaded and
installed so that the rest of the installation process can be finished in the chosen language. After choosing
a language, click Save and continue.

3. Select an installation profile. Installation profiles provide site features and functions for a specific type
of site as a single download containing the core software, contributed modules, themes, and pre-defined
configuration. Core contains two installation profiles. Select the core Standard installation profile. Click
Save and continue.

20
CHAPTER 3. 安装 3.4. RUNNING THE INSTALLER

4. The next step in the installer will verify that your system meets the minimum requirements. If it does
not, you’ll be presented with an outline of what needs to be corrected in order to proceed. If it does, the
installer will automatically advance to the next step.
5. Provide details of the database you created in the Section 3.3,“Preparing to Install”chapter. Then click
Save and continue.

Field name Explanation Value

Database name The custom name given to the drupal8
database
Database username Username created databaseUsername
Database password Password chosen

21
CHAPTER 3. 安装 3.4. RUNNING THE INSTALLER

6. The next step will display a progress bar under the heading Installing Drupal. After the installer has
completed, it will automatically advance to the next step.

22
CHAPTER 3. 安装 3.4. RUNNING THE INSTALLER

7. The final step is to configure some basic information about your new site. Note that the user account you
create in this step is the site’s admin account. See Section 7.2, “Concept: The User 1 Account”for
important information about this unique account. You can safely name this account ”admin”, and make
sure to choose a secure and unique password.
Fill in the form with the following information:

Field name Explanation Value

Site name The name chosen for the site Anytown Farmers Market
Site email address The email associated with the [email protected]
site
Username The designated user’s admin
credentials
Password The password chosen
Confirm password Repeat the password
Email address The user’s email [email protected]

The remaining fields can likely be left at their default values.

23
CHAPTER 3. 安装 3.4. RUNNING THE INSTALLER

24
CHAPTER 3. 安装 3.4. RUNNING THE INSTALLER

8. Click Save and continue.

9. You will be redirected to the front page of your new site and you should see the message Congratulations,
you installed Drupal! displayed at the top of the page.

Expand your understanding

Check the Status Report to see if there are any problems with the installation. See Section 12.5, “Concept:
Status Report”.

Related concepts
• Section 11.7, “Concept: Development Sites”
• Section 3.2, “Concept: Additional Tools”

Additional resources
Drupal.org community documentation page ”Create A Database”
Attributions
Written and edited by Joe Shindelar at Drupalize.Me, and Jojy Alphonso at Red Crackle.

25
Chapter 4

基本站点配置

4.1 Concept: Administrative Overview

Prerequisite knowledge
• Section 1.3, “概念：主题”

• Section 1.2, “概念：模块”

What is the administrative menu?

The toolbar provided by the core Toolbar module displays the Manage administrative menu at the top or left
side of the site, for users with permission to see it. This menu provides access to all of the administrative
areas of the site. The menu entries will vary depending on which modules are active on your site and the
permissions of the person viewing the menu; if you install using the core Standard installation profile and have
full administrative permissions, the top-level entries are as follows:

Content Lists and manages existing content, and allows creation of new content.
Structure Contains a list of links for managing structural elements of the site, such as blocks, content types,
menus, and taxonomy.

Appearance Manages themes and appearance-related settings.

Extend Manages the installation and uninstallation of modules.
Configuration Contains links to settings pages for various site features.
People Manages users, roles, and permissions.

Reports Contains links to logs, update information, search information, and other information about the
site’s status.
Help Lists help topics for installed modules that provide them.
The arrow button on the far right side of the second line of the toolbar (or far left side, if the site is
being viewed using a right-to-left-reading language like Arabic) can be used to switch the menu from appearing
horizontally at the top of the page, to a vertical format on the left side (or right side, in right-to-left languages).
When viewed vertically, the menu becomes an interactive tree.

27
CHAPTER 4. 基本站点配置 4.1. CONCEPT: ADMINISTRATIVE OVERVIEW

28
CHAPTER 4. 基本站点配置 4.1. CONCEPT: ADMINISTRATIVE OVERVIEW

This guide has a standard way to describe navigation to administrative pages using the administrative
toolbar. See the section called “Conventions of the Guide”for more information.

What are contextual links?

Some administrative and editing functionality on the site can be accessed through the contextual links displayed
by the core Contextual Links module. Contextual links take you to some of the same pages that you can access
through the administrative menu, but instead of having to navigate through the menu hierarchy, these links are
provided near where the related content is displayed on your site.
Contextual links have to be activated to be visible. If your site’s theme uses the default styling for contextual
links, a pencil icon is used to indicate that contextual links are present and activated, and if you click the icon,
you will see the contextual links. There are two ways to activate the pencil icons that provide access to the
contextual links:
• If you are using a mouse in a browser, the icon will temporarily appear when you hover over an area that
has related contextual links.
• You can click the master pencil icon (or its Edit link) at the right end of the top bar in the toolbar,
which will activate all of the contextual links on the current page. This icon is only visible on pages with
contextual links.

29
CHAPTER 4. 基本站点配置 4.2. EDITING BASIC SITE INFORMATION

Attributions
Written by Scott Wilkinson and Jennifer Hodgdon.

4.2 Editing Basic Site Information

Goal
Change basic site information such as Site name, Slogan, Default time zone.

Prerequisite knowledge
Section 4.1, “Concept: Administrative Overview”

30
CHAPTER 4. 基本站点配置 4.2. EDITING BASIC SITE INFORMATION

Steps
Configuring the basic site information
1. In the Manage administrative menu, navigate to Configuration > System > Basic site settings (admin/config/system/site
information) to change the Site name, Slogan, administrative Email address, or the Default front page
path.
2. Fill in the available fields as appropriate for your site.

Field name Explanation Example value

Site name Used to identify the site and Anytown Farmers Market
displayed in browsers
Slogan Usually displayed sitewide Farm Fresh Food
Email address Used as From address in [email protected]
automated email messages
(registrations, password resets,
etc)

3. After editing the fields, click Save configuration to see the changes applied to the site.

Configuring default Regional settings

1. In the Manage administrative menu, navigate to Configuration > Regional and language > Regional
settings (admin/config/regional/settings).
2. Select the appropriate country from the Default country select list in the Locale section, and set which
day will be displayed as First day of week on your site.
3. In the Time zones section, select the sitewide Default time zone from the list and configure user-specific
time zones.

31
CHAPTER 4. 基本站点配置 4.3. INSTALLING A MODULE

4. After editing the fields, click Save configuration to see the changes applied to the site.

Additional resources
Drupal.org community documentation page ”Getting started with Drupal 8 administration”
Attributions
Written and edited by Sree Veturi, Michael Lenahan at erdfisch, and Antje Lorch.

4.3 Installing a Module

Goal
Install a core module, or a contributed module whose files have already been uploaded to the site, through the
administrative interface or using Drush.

32
 CHAPTER 4. 基本站点配置 4.3. INSTALLING A MODULE

Prerequisite knowledge
Section 1.2, “概念：模块”

Site prerequisites
If you want to use Drush to install modules, Drush must be installed. See Section 3.2, “Concept: Additional
Tools”.

Steps
You can use the administrative interface or Drush to install modules.

Using the administrative interface

1. In the Manage administrative menu, navigate to Extend (admin/modules). The Extend page appears
showing all the available modules in your site.
2. Check the boxes for the module or modules you want to install. For example, check the box for the core
Activity Tracker module.

3. Click Install. The checked modules will be installed.

Using Drush
1. In the Manage administrative menu, navigate to Extend (admin/modules). The Extend page appears
showing all the available modules in your site.
2. Find the machine name of the module you want to install, by expanding the information area for the
module. For instance, the core Activity Tracker module’s machine name is tracker.
3. Run the following Drush command to install the module:
drush en tracker

Expand your understanding

If you do not see the effect of these changes in your site, you might need to clear the cache. See Section 12.2,
“Clearing the Cache”.

Additional resources
Drush
Attributions
Written and edited by Boris Doesborg and Jennifer Hodgdon.

33
CHAPTER 4. 基本站点配置 4.4. UNINSTALLING UNUSED MODULES

4.4 Uninstalling Unused Modules

Goal
Uninstall the core Search and History modules, as well as the core Activity Tracker module if you installed it
in Section 4.3, “Installing a Module”, to reduce overhead.

Prerequisite knowledge
Section 1.2, “概念：模块”

Site prerequisites
• You must have at least one unused module on your site that you want to uninstall, such as the core Search
module.
• If you want to use Drush to uninstall modules, Drush must be installed. See Section 3.2, “Concept:
Additional Tools”.

Steps
You can use the administrative interface or Drush to uninstall modules.

Using the administrative interface

1. In the Manage administrative menu, navigate to Extend > Uninstall (admin/modules/uninstall) where
you will find the list of modules that are ready to be uninstalled.
2. Check the boxes for the modules you are uninstalling (Search, History, and Activity Tracker). Click
Uninstall at the bottom of the page.

Note
You cannot uninstall a module if it is required by some other module(s) and/or func-
tionality. For example, the core File module is required by the core Text Editor,
CKEditor, and Image modules. It can’t be uninstalled unless you uninstall its depen-
dent module(s) and functionality first. A module that cannot be uninstalled yet will
have a disabled checkbox, restricting you from uninstalling it.

3. Step 2 will prompt you to confirm the module uninstall request. Click Uninstall.

34
CHAPTER 4. 基本站点配置 4.4. UNINSTALLING UNUSED MODULES

35
CHAPTER 4. 基本站点配置 4.5. CONFIGURING USER ACCOUNT SETTINGS

Using Drush
1. In the Manage administrative menu, navigate to Extend (admin/modules). The Extend page appears
showing all the available modules in your site.
2. Find the machine name of the module you want to uninstall, by expanding the information area for the
module. For instance, the core Activity Tracker module’s machine name is tracker.
3. Run the following Drush command to uninstall the module:
drush pm - uninstall tracker

Expand your understanding

• Section 3.2, “Concept: Additional Tools”

• Section 12.2, “Clearing the Cache”

• You can also uninstall the core Comment module by following these steps, but only after comment fields
have been removed, which is a side effect of Section 6.2, “Deleting a Content Type”.

Attributions
Written and edited by Surendra Mohan, and Jojy Alphonso at Red Crackle.

4.5 Configuring User Account Settings

Goal
Turn off the ability for people to register user accounts on the site. Also, review and/or edit the email messages
generated by the site for events related to user accounts.

Prerequisite knowledge
Section 4.1, “Concept: Administrative Overview”

Steps
1. In the Manage administrative menu, navigate to Configuration > People > Account settings (admin/con-
fig/people/accounts).
2. Under Registration and cancellation, select Administrators only as the people with permissions to register
user accounts. You can check Require email verification when a visitor creates an account in case you
want to change the settings for account registration later on.

36
CHAPTER 4. 基本站点配置 4.5. CONFIGURING USER ACCOUNT SETTINGS

3. Optionally, change the default email address from which user account notifications from the farmers
market website will be sent. This will help you maintain a separate email address from the one used for
the website in general. For example, this email address for user account notifications will be useful for a
staff member(s) communicating with vendors.

4. Optionally, edit the email templates in the Emails section to customize automated emails. There are seven
email templates available with the core. They are meant for different user-specific occasions. All of them
can be personalized and three can be disabled via checkboxes: activation, blocking, and cancellation.
You can send out your own text (for example, welcoming the new vendors for whom accounts were just
created) by editing the the Welcome (new user created by administrator) template.

37
CHAPTER 4. 基本站点配置 4.6. CONFIGURING THE THEME

5. Click Save configuration to save the changes.

Expand your understanding

• Section 12.2, “Clearing the Cache”
• Section 7.4, “Creating a User Account”

Related concepts
See Chapter 7, 管理用户账号 for more information about user accounts and permissions.

Additional resources
Security Guide can help you with a more safety-focused approach to configuration.
Attributions
Written and edited by Laura Vass at Pronovix, and Jojy Alphonso at Red Crackle.

4.6 Configuring the Theme

Goal
Edit the settings of the default core Bartik theme to change the color scheme and to add a logo.

Prerequisite knowledge
Section 1.3, “概念：主题”

Steps
1. In the Manage administrative menu, navigate to Appearance (admin/appearance).

38
CHAPTER 4. 基本站点配置 4.6. CONFIGURING THE THEME

2. Under Installed themes, you will find Bartik listed as your default theme. Under Bartik (default theme),
click Settings.

3. Under Color scheme, click inside each color build box and type the proper color codes you would like to
add. For example, use the following colors:

Area Color
Header background top #7db84a (green)
Header background bottom #2a3524 (dark green)
Main background #ffffff (white)
Sidebar background #f8bc65 (light orange)
Sidebar borders #e96b3c (orange)
Footer background #2a3524 (dark green)
Title and slogan #ffffff (white)
Text color #000000 (black)
Link color #2a3524 (dark green)

Note: You can also use the color wheel on the right to select colors of your choice. The web color codes
will be added for you.

4. Under Logo image, uncheck Use the logo supplied by the theme.

39
CHAPTER 4. 基本站点配置 4.6. CONFIGURING THE THEME

5. Under Upload logo image, locate a logo file and upload it to your site. Note: You can also set a universal
logo for all themes under Appearance > Settings (admin/appearance/settings). A custom logo for your
theme will override the universal logo.
Once you have selected the file you would like to upload, you will see its filename next to the Choose File
or Browse button in your browser.
6. In order to save your changes and see the updated colors and logo on your site, click Save configuration
at the bottom of the page.
Note: Under Color scheme, there is a Preview section that displays a sample of how your website will
look with the new settings.
core Bartik theme settings preview
7. Click Return to site or Home in the toolbar to verify that you have updated the core Bartik theme settings
for your website.

40
CHAPTER 4. 基本站点配置 4.6. CONFIGURING THE THEME

Expand your understanding

• Section 11.4, “Finding Themes”
• Section 11.5, “Downloading and Installing a Theme from Drupal.org”
• If you do not see the effect of these changes in your site, you might need to clear the cache. See Section 12.2,
“Clearing the Cache”.

Attributions
Written and edited by Ann Greazel, Amanda Luker at Advomatic, and Jack Haas.

41
Chapter 5

基本页面管理

5.1 Concept: Paths, Aliases, and URLs

What is a URL?
URL is the abbreviation for ”Uniform Resource Locator”, which is the page’s address on the web. It is the
”name” by which a browser identifies a page to display. In the example ”Visit us at example.com.”, example.com
is the URL for the home page of your website. Users use URLs to locate content on the web.

What is a Path?
A path is the unique, last part of the URL for a specific function or piece of content. For example, for a page
whose full URL is http://example.com/node/7, the path is node/7.
Here are some examples of paths you might find in your site:
• node/7
• taxonomy/term/6

• admin/content/comment
• user/login
• user/3

What is an Alias?
The core software has a feature called ”URL Alias” that allows you to provide a more understandable name to
the content. So, if you have an ”About Us” page with the path node/7, you can set up an alias so that your
visitors will see it as http://www.example.com/AboutUs. The core Path module, which supports URL aliasing,
provides this functionality.

Related topics
• Section 5.2, “Creating a Content Item”

• Section 5.3, “Editing a Content Item”

Attributions
Adapted by Diána Lakatos at Pronovix from ”URL aliases”, and ”Understanding Drupal paths” copyright
2000-2017 by the individual contributors to the Drupal Community Documentation

43
CHAPTER 5. 基本页面管理 5.2. CREATING A CONTENT ITEM

5.2 Creating a Content Item

Goal
Create and publish a content item that will be used as the home page of the site.

Prerequisite knowledge
Section 5.1, “Concept: Paths, Aliases, and URLs”

Site prerequisites
The Basic page content type must exist. This is created on your site when you install with the core Standard
installation profile.

Steps
1. In the Manage administrative menu, navigate to Content > Add content > Basic page (node/add/page).
The Create Basic page form appears.
2. Click Edit summary.
3. Fill in the fields as shown below.

Field name Explanation Value

Title Title of the page. Will also be Home
used as a meta tag in the
source code, URL alias, and as
label of the content item in
administration screens
Summary Summary of the value of the Opening times and location of
body field. Can be used as City Market.
teaser in overview pages
Body Full content of the page Welcome to City Market - your
neighborhood farmers market!
Open: Sundays, 9 AM to 2
PM, April to September
Location: Parking lot of Trust
Bank, 1st & Union, downtown
URL path settings > URL Alternate relative path for the /home
alias content

By clicking the Source button in the rich text editor toolbar, you can see the HTML source code of the
text that you are editing.

44
CHAPTER 5. 基本页面管理 5.2. CREATING A CONTENT ITEM

4. Click Preview to ensure everything looks like expected.

5. Click Back to content editing.

6. Click Save and publish. The content is saved and can be found on the Content page.
7. Follow the same steps to create an About page, with title ”About”, and a body telling about the history
of the farmer’s market.

Expand your understanding

• Section 5.5, “Designating a Front Page for your Site”
• Section 5.7, “Adding a Page to the Navigation”
• Section 10.4, “Translating Content”

Related concepts
• Section 10.1, “Concept: User Interface, Configuration, and Content translation”

• Section 5.1, “Concept: Paths, Aliases, and URLs”

• Section 5.3, “Editing a Content Item”

45
CHAPTER 5. 基本页面管理 5.3. EDITING A CONTENT ITEM

Additional resources
Drupal.org community documentation page ”About nodes”
Attributions
Written by Agnes Kiss and Boris Doesborg.

5.3 Editing a Content Item

Goal
Update the hours on the Home page content item.

Prerequisite knowledge
Section 5.2, “Creating a Content Item”

Site prerequisites
A content item for the Home page must exist. See Section 5.2, “Creating a Content Item”.

Steps
1. In the Manage administrative menu, navigate to Content (admin/content).

2. If the content item you want to edit was updated or created recently, it should appear near the top of the
content list on that page. If not, you can use the Content type, Title, or other filters to locate the content
item.

3. Click Edit in the row of the content item you want to edit (Home), to open the content editing form.
Update the opening hours in the Body field. See Section 5.2,“Creating a Content Item”for an explanation
of the fields and a screenshot.

4. Check Create new revision in the box on the right, if it is not already checked, and enter a Revision
log message explaining what changes you are making (for example, you might enter ”Updated opening
hours”). This text will appear in the revision log for the page.

46
CHAPTER 5. 基本页面管理 5.4. EDITING WITH THE IN-PLACE EDITOR

5. Click Save and keep published to save your changes.

6. You will be redirected back to the Content administrative page, and there should be a message showing
that the content item was updated.

Expand your understanding

As an alternative to the first two steps above, you can also reach the content edit form as follows:
1. Starting from your site’s home page, use the site’s navigation menus to locate the page where the content
you want to edit is displayed to visitors.
2. Most themes will display an Edit link or tab near the top of that page to people with permission to edit
the page; clicking the link will take you to the full content edit form.
3. You could also use the in-place editor (refer to Section 5.4, “Editing with the In-Place Editor”) from
this page.
Attributions
Written by Chris Dart and Jennifer Hodgdon.

5.4 Editing with the In-Place Editor

Goal
Use the in-place editor to add information to the About page without opening the full editor page.

Prerequisite knowledge
• Section 2.3, “Concept: Content Entities and Fields”
• Section 5.2, “Creating a Content Item”
• Section 5.3, “Editing a Content Item”
• Section 4.1, “Concept: Administrative Overview”

47
CHAPTER 5. 基本页面管理 5.4. EDITING WITH THE IN-PLACE EDITOR

Site prerequisites
The About page you want to edit must exist. See Section 5.2, “Creating a Content Item”.

Steps
Navigate to the About page to edit content with the in-place editor. If the page has not yet been added to a
navigation menu, you can find and open it by following these steps:

1. In the Manage administrative menu, navigate to Content (admin/content).

2. If the content item you want to edit was updated or created recently, it should appear near the top of the
content list on that page. If not, you can use Type, Title, or other filters to locate the content item.
3. Find the About page and click it.

Once the content you want to edit is being viewed in your browser, follow these steps to use the quick editor:
1. Find the section of the page that displays the content you want to edit, and turn on quick editing mode
using the Quick edit contextual link (see Section 4.1,“Concept: Administrative Overview”for instructions
on how to access contextual links). You will see each editable field on this content item outlined in blue;
also, a hovering dialog box will appear.

2. Click the Body text area to begin editing. The Body field supports a rich text editor. The editing toolbar
will be displayed in a hovering dialog box.
3. Add some information about City Market. A Save button will appear in the hovering dialog box, and the
field outline will change color.

4. If you are satisfied with your edits, click Save in the hovering dialog box. If not, click ”x” to discard your
edits, and confirm. Either way, quick editing mode will be turned off.

Expand your understanding

Try using the full editor on the same content (see Section 5.3, “Editing a Content Item”) and note that there
is much more information that can be edited that is not available in the quick editor.
Attributions
Written and edited by David Lee and Jennifer Hodgdon.

48
CHAPTER 5. 基本页面管理 5.5. DESIGNATING A FRONT PAGE FOR …

5.5 Designating a Front Page for your Site

Goal
Configure which content item is displayed as the front page of your website.

Site prerequisites
The content item that you want to designate as the front page of your site must exist. See Section 5.2,“Creating
a Content Item”.

Steps
1. In the Manage administrative menu, navigate to Configuration > System > Basic site settings (admin/config/system/site
information).
2. Under Front page, replace /node with the name of the page you would like to make the home page. To
use the home page that was previously created, provide its path /home. Click Save configuration.

3. Navigate to the home page to verify that it displays content as configured by you.

49
CHAPTER 5. 基本页面管理 5.6. CONCEPT: MENU

Expand your understanding

• Section 5.7, “Adding a Page to the Navigation”

• Follow Section 5.2, “Creating a Content Item”to create an error page to be used as a 404 (page not
found) or 403 (not authorized) response on your site. Then following the steps here, you can designate it
as the error response, in the Error pages section of the configuration.

Related concepts
Section 5.6, “Concept: Menu”
Attributions
Written and edited by Ann Greazel, Jack Haas, and Jojy Alphonso at Red Crackle.

5.6 Concept: Menu

What is a menu?
Menus are a collection of links (menu items) used to navigate a website. The core Menu UI module provides an
interface to control and customize the menu system. Menus are primarily displayed as a hierarchical list of links.
By default, new menu items are placed inside a built-in menu labeled Main navigation, but administrators can
also create custom menus.
The core Standard installation profile contains five menus:
Main navigation Links to sections intended for site visitors. They are usually created by site administrators.
Administration Links to administrative tasks. This menu mainly contains links supplied by modules on
your site.
User account menu Links to tasks associated with the user account such as My account and Log out.
Footer Links to important pages within the site intended for the footer. They are usually created by site
administrators.

Tools Links to tasks necessary for site visitors. Some modules feature their links here.
You can customize menus in the following ways, using the menu administration functionality:
• Creating new custom menus.
• Adding new menu items.

• Reordering menu items by setting their ”weight” or by dragging them into place.
• Renaming menu items.
• Changing the link title (the tooltip that appears when you mouse over a menu item).

• Moving a menu item into a different menu by editing its Parent property.
A menu item will only be shown to a visitor if they have the rights to view the page it links to. For example,
the admin menu item is not shown to visitors who are not logged in.

Related topics
• Section 5.7, “Adding a Page to the Navigation”
• Section 5.8, “Changing the Order of Navigation”

50
CHAPTER 5. 基本页面管理 5.7. ADDING A PAGE TO THE NAVIGATION

• To display a menu, you will need to place the block that corresponds to the menu in a region of your theme;
see Section 8.1, “Concept: Blocks”, Section 2.1, “Concept: Regions in a Theme”, and Section 8.3,
“Placing a Block in a Region”. The core Standard installation profile places all of the menus it defines
except Administration in regions of the core Bartik theme. The core Toolbar module, which is installed
by the core Standard installation profile, displays the Administration menu; it is also displayed by the
contributed Admin Toolbar module.

Attributions
Written and edited by Ajay Viswambharan, Jojy Alphonso at Red Crackle, and Jennifer Hodgdon.

5.7 Adding a Page to the Navigation

Goal
Add a page to the navigation. For example, the About page.

Prerequisite knowledge
• Section 5.6, “Concept: Menu”
• Section 5.3, “Editing a Content Item”

Site prerequisites
The About page content item must exist. See Section 5.2, “Creating a Content Item”.

Steps
1. In the Manage administrative menu, navigate to Content (admin/content).
2. Find the About page, and click Edit in that row. The content editing form appears.

3. Click Menu settings on the right to expand it.

4. Check Provide a menu link for the menu options to appear.
5. Enter values from the table below:

Field name Explanation Example value

Menu link title Title that will be displayed in About
the menu
Description Text that will be displayed History of the market
when a visitor hovers over the
link
Parent item Location of the page in the <Main navigation>
menu hierarchy. For example,
if you choose <Main
navigation>, the page will
appear in the highest level of
the navigation. By choosing
another menu item as parent,
you can create a menu
hierarchy of multiple levels.
51
CHAPTER 5. 基本页面管理 5.7. ADDING A PAGE TO THE NAVIGATION

Field name Explanation Example value

Weight The order in which the page -2
should appear in the menu
(lower-weighted menu items
will be shown before
higher-weighted menu items)

6. Click Save and keep published to save the changes. Click Home or Return to site in the navigation bar to
see the result, which could look like the picture below.

52
CHAPTER 5. 基本页面管理 5.8. CHANGING THE ORDER OF NAVIGATION

Expand your understanding

Section 5.8, “Changing the Order of Navigation”

Additional resources
Drupal.org community documentation page ”Working with menus”
Attributions
Adapted by Boris Doesborg from ”Working with Menus”, copyright 2000-2017 by the individual contributors
to the Drupal Community Documentation; edited by Jack Haas.

5.8 Changing the Order of Navigation

Goal
Reorder the items in a menu.

Prerequisite knowledge
• Section 5.6, “Concept: Menu”
• Section 5.7, “Adding a Page to the Navigation”

Site prerequisites
Home and About pages must exist in the main navigation menu. See Section 5.7, “Adding a Page to the
Navigation”.

53
CHAPTER 5. 基本页面管理 5.8. CHANGING THE ORDER OF NAVIGATION

Steps
1. In the Manage administrative menu, navigate to Structure > Menus (admin/structure/menu) where all
menus on your site are listed. Click Edit Menu from the Operations dropdown for Main navigation. You
can also reach this page using contextual links (refer to Section 4.1,“Concept: Administrative Overview”
) for the menu.

2. The Edit menu page will display a list of each item in the menu you chose (Main navigation).

3. Use the cross bar handles to reorder the menu items. Drag the Home menu item above the About menu
item so that it appears first.

54
CHAPTER 5. 基本页面管理 5.8. CHANGING THE ORDER OF NAVIGATION

4. Click Save.

5. The home page now displays the main navigation with the Home menu item displayed first.

Expand your understanding

Add a menu item called Contact, leading to the /contact page, to your Main navigation menu. The contact page
is provided by the core Contact module; you may want to edit its layout and fields (see Section 6.9,“Changing
Content Entry Forms”).

Related concepts
Section 5.6, “Concept: Menu”

55
CHAPTER 5. 基本页面管理 5.8. CHANGING THE ORDER OF NAVIGATION

Attributions
Written by Ann Greazel.

56
Chapter 6

内容结构

6.1 Adding a Content Type

Goal
Add and configure a new content type Vendor.

Prerequisite knowledge
Section 2.3, “Concept: Content Entities and Fields”

Site prerequisites
You need to have a plan in place for your content structure. See Section 2.5,“Planning your Content Structure”
.

Steps
1. In the Manage administrative menu, navigate to Structure > Content types (admin/structure/types). The
Content types page appears showing all the available types of content.

2. Click Add content type. The Add content type page appears. Fill in the fields as shown below.

Field name Explanation Example value

Name Name of the content type Vendor
Description Explain the use of the content Information about a vendor
type

57
CHAPTER 6. 内容结构 6.1. ADDING A CONTENT TYPE

3. In the vertical tab Submission form settings, configure the form that is used for creating and editing
content of this type. Fill in the fields as shown below.

Field name Explanation Example value

Title field label Label of the Title field that is Vendor name
shown when editing or creating
content of this type.
Preview before submitting Option to choose whether you Optional
should preview the content
before submitting.
Explanation or submission Instructions for creating or (Leave blank)
guidelines editing content.

58
CHAPTER 6. 内容结构 6.1. ADDING A CONTENT TYPE

4. In the vertical tab Publishing options, decide on default options for new content of this type. Fill in the
fields as shown below.

Field name Explanation Example value

Published Make the content item Checked
published by default.
Promoted to front page In a default website, this Unchecked
setting can be used to show
content on the homepage.
Sticky at top of lists In a default website, this Unchecked
setting can be used to keep
content on top of a list.
Create new revision Create a new revision each Checked
time the vendor is being
edited.

Changing these settings does not affect the content items that have already been created.

59
CHAPTER 6. 内容结构 6.1. ADDING A CONTENT TYPE

5. In the vertical tab Display settings, decide if the author and publication date will be visible in the content
item. Fill in the fields as shown below.

Field name Explanation Example value

Display author and date Display the author username Unchecked
information and publication date on each
vendor page.

6. In the vertical tab Menu settings, fill in the fields as shown below.

Field name Explanation Example value

Available menus Menus that this type of content Unchecked
can be added to. Vendors do
not need to appear in menus,
so uncheck all menu options.

60
CHAPTER 6. 内容结构 6.1. ADDING A CONTENT TYPE

7. Click Save and manage fields to save the content type. The Manage fields page appears that allows you
to add fields to the content type. See Section 6.3, “Adding Basic Fields to a Content Type”

8. Follow the same steps to create a content type for recipes. Example values for the fields in the forms,
where they are different from the steps above:

Field name Example value

Name Recipe
Description A recipe submitted by a vendor
Submission form settings - Title Recipe name

Expand your understanding

• Section 6.3, “Adding Basic Fields to a Content Type”
• Install and configure the contributed Pathauto module so that content items get automatically generated
URLs/path aliases. See Section 5.1,“Concept: Paths, Aliases, and URLs”for more on URLs within your
site, Section 11.1, “Finding Modules”for instructions on finding contributed modules, and Section 11.3,
“Downloading and Installing a Module from Drupal.org”for instructions on downloading and installing
contributed modules.
Attributions
Written and edited by Sree Veturi, Boris Doesborg, and Jennifer Hodgdon.

61
CHAPTER 6. 内容结构 6.2. DELETING A CONTENT TYPE

6.2 Deleting a Content Type

Goal
Delete the unneeded content type Article.

Prerequisite knowledge
Section 4.1, “Concept: Administrative Overview”

Site prerequisites
The Article content type must exist. It is created on your site when you install with the core Standard installation
profile.

Steps
1. In the Manage administrative menu, navigate to Structure > Content types (admin/structure/types). The
Content types page appears.
2. Click Delete in the Operations dropdown button for the Article content type.

3. A confirmation page is displayed. Click Delete.

62
CHAPTER 6. 内容结构 6.2. DELETING A CONTENT TYPE

63
CHAPTER 6. 内容结构 6.3. ADDING BASIC FIELDS TO A CONTENT …

4. The Content types page appears with a confirmation message saying that the content type has been
deleted:

Attributions
Written and edited by Sree Veturi and Boris Doesborg.

6.3 Adding Basic Fields to a Content Type

Goal
Add a link field and an image field to the Vendor content type.

Prerequisite knowledge
Section 2.3, “Concept: Content Entities and Fields”

Site prerequisites
The Vendor content type must exist. See Section 6.1, “Adding a Content Type”.

Steps
Add the fields Vendor URL and Main image to the Vendor content type.
1. In the Manage administrative menu, navigate to Structure > Content types (admin/structure/types). Then
click Manage fields in the dropdown button for the Vendor content type. The Manage fields page appears.

2. Click Add field. The Add field page appears. You can either create a new field for the content type or
re-use an existing field.
3. Fill in the fields as shown below.

Field name Explanation Value

Add a new field Field type Link
Label Label that is visible in Vendor URL
administration pages

A machine name is automatically generated, based on the Label value. Click Edit if you want to override
the default name.

64
CHAPTER 6. 内容结构 6.3. ADDING BASIC FIELDS TO A CONTENT …

4. Click Save and continue. The page Vendor URL appears which lets you set the allowed number of values.
Fill in the fields as shown below.

Field name Explanation Value

Allowed number of values The number of values that can Limited, 1
be entered

5. Click Save field settings. The page Vendor URL settings for Basic page appears which allows you to
configure the field. Fill in the fields as shown below.

Field name Explanation Value

Label Label that is visible in the Vendor URL
content form
Help text The instruction that is shown (leave blank)
below the field
Required field Whether the field is required Unchecked
or not

65
CHAPTER 6. 内容结构 6.3. ADDING BASIC FIELDS TO A CONTENT …

Field name Explanation Value

Allowed link type The kind of links that can be External links only
entered
Allow link text Whether a link text can be Disabled
entered

66
CHAPTER 6. 内容结构 6.3. ADDING BASIC FIELDS TO A CONTENT …

67
CHAPTER 6. 内容结构 6.3. ADDING BASIC FIELDS TO A CONTENT …

6. Click Save settings. The Vendor URL has been added to the content type. Continue creating the Main
image field.

7. Click Add field. The Add field page appears. Fill in the fields as shown below.

Field name Explanation Value

Add a new field Field type Image
Label Label that is visible in Main image
administration pages

8. Click Save and continue. The page Main image appears. Fill in the fields as shown below.

Field name Explanation Value

Allowed number of values The number of values that can Limited, 1
be entered

You can set a default image here. This will be used when you do not provide an image when creating a
Vendor content item.
9. Click Save field settings. The page Main image settings for Basic page appears. Fill in the fields as shown
below.

Field name Explanation Value

Label Label that is visible in the Main image
content form
Help text The instruction that is shown (leave blank)
below the field
Required field Whether the field is required Checked
or not
Allowed file extensions The type of images that can be png, gif, jpg, jpeg
uploaded
File directory The directory where the files vendors
will be stored. By providing a
file directory value, you ensure
that all images uploaded via
the Main image field will be
located in the same directory.
Minimum image resolution The minimum resolution of the 600 x 600
uploaded image
Maximum upload size The maximum file size of the 5 MB
uploaded image
Enable Alt field Whether an alternative text Checked
can be entered
Alt field required Whether an alternative text is Checked
required

68
CHAPTER 6. 内容结构 6.3. ADDING BASIC FIELDS TO A CONTENT …

69
CHAPTER 6. 内容结构 6.4. CONCEPT: REFERENCE FIELDS

10. Click Save settings. Main image has been added to the content type.

11. Add a Main image field to the Recipe content type, using similar steps. Start by navigating to the Recipe
content type’s Manage Fields page in step 1. Then skip to step 7 and follow the remaining steps, but
reuse the existing Main image field you created for the Vendor content type rather than creating a new
field. In subsequent steps, some of the configuration screens will not be available, because of the field
reuse.
12. Create two Vendor content items (see Section 5.2, “Creating a Content Item”) called ”Happy Farm”
and ”Sweet Honey”. Make sure that they include images and URLs.

Expand your understanding

• Section 6.12, “Concept: Image Styles”

• Section 6.11, “Changing Content Display”

• Section 6.9, “Changing Content Entry Forms”

Additional resources
Drupal.org community documentation page ”Add a field to a content type”
Attributions
Written by Sree Veturi and Boris Doesborg.

6.4 Concept: Reference Fields

Prerequisite knowledge
Section 2.3, “Concept: Content Entities and Fields”

What is a reference field?

A reference field is a field that represents a relationship between an entity and one or more other entities, which
may belong to the same or different entity type. The three most commonly-used reference fields are:

70
CHAPTER 6. 内容结构 6.5. CONCEPT: TAXONOMY

Content reference A reference to a content item. For example, you might want to connect recipes to the
vendors who submitted them. You would set up a content reference field called Submitted by referencing
Vendor content items on the Recipe content type.
Taxonomy term reference A reference to a taxonomy term. For example, you might want to connect
recipes to their ingredients. You would set up a taxonomy term reference field called Ingredients on the
Recipe content type. This reference field will point to the vocabulary Ingredients.

User reference A reference to a user account. For example, you might want to connect recipes with their
chefs. You would set up a user reference field called Chefs on the Recipe content type.

Related topics
Section 6.5, “Concept: Taxonomy”
Attributions
Written and edited by Surendra Mohan, and Jojy Alphonso at Red Crackle.

6.5 Concept: Taxonomy

Prerequisite knowledge
• Section 2.3, “Concept: Content Entities and Fields”
• Section 6.4, “Concept: Reference Fields”

What is Taxonomy?
Taxonomy is used to classify website content. One common example of taxonomy is the tags used to classify
or categorize posts in a blog website; the farmers market website could use an ingredients taxonomy to classify
recipes. Individual taxonomy items are known as terms (the blog tags or recipe ingredients in these examples);
and a set of terms is known as a vocabulary (the set of all blog post tags, or the set of all recipe ingredients in
these examples). Technically, taxonomy terms are an entity type and the entity subtypes are the vocabularies.
Like other entities, taxonomy terms can have fields attached; for instance, you could set up an image field to
contain an icon for each term.
An individual vocabulary can organize its terms in a hierarchy, or it could be flat. For example, blog
tags normally have a flat structure, while a recipe ingredients vocabulary could be hierarchical (for example,
tomatoes could be a sub-term of vegetables, and under tomatoes, you could have green and red tomatoes).
Taxonomy terms are normally attached as reference fields to other content entities, which is how you can
use them to classify content. When you set up a taxonomy reference field, you can let users enter terms in two
ways:
Free tagging New terms can be created right on the content editing form.

Fixed list of terms The list of terms is curated and managed outside the content editing form, and users
can only choose from the existing list when editing content.
Taxonomy reference fields can be added to any entity, such as user accounts, custom blocks, or regular
content items. If you use them to classify regular content items, your site will automatically be set up with
taxonomy listing pages for each term; each of these pages lists all of the content items that are classified with
that term. For example, if you created several recipes that all had carrots as an ingredient, you might see
something like this on the Carrots taxonomy listing page:

71
CHAPTER 6. 内容结构 6.5. CONCEPT: TAXONOMY

72
CHAPTER 6. 内容结构 6.6. SETTING UP A TAXONOMY

Related topics
• Section 6.6, “Setting Up a Taxonomy”.
• The listing pages are views, which are covered in Chapter 9, 用视图创建列表.
Attributions
Adapted and edited by Surendra Mohan, Jennifer Hodgdon, and Jojy Alphonso at Red Crackle from ”Orga-
nizing content with taxonomies” and ”About taxonomies”, copyright 2000-2017 by the individual contributors
to the Drupal Community Documentation.

6.6 Setting Up a Taxonomy

Goal
Create an Ingredients vocabulary and add it to the Recipe content type as a field that can contain an unlimited
number of values and that allows adding new terms to the vocabulary.

Prerequisite knowledge
• Section 2.3, “Concept: Content Entities and Fields”
• Section 6.5, “Concept: Taxonomy”
• Section 6.3, “Adding Basic Fields to a Content Type”

Site prerequisites
The Recipe content type must exist. See Section 6.1, “Adding a Content Type”.

Steps
1. In the Manage administrative menu, navigate to Structure > Taxonomy (admin/structure/taxonomy).
You will see the Tags vocabulary that was created with the core Standard installation profile.

73
CHAPTER 6. 内容结构 6.6. SETTING UP A TAXONOMY

2. Click Add vocabulary, and fill in the values below.

Field name Explanation Example value

Name The name of the vocabulary Ingredients
Description A brief note about the (Leave blank)
vocabulary

3. Click Save. You will be taken to the Ingredients page, which shows a list of all the terms in this vocabulary.

74
CHAPTER 6. 内容结构 6.6. SETTING UP A TAXONOMY

4. Click Add term. Enter ”Butter” in the Name field. Click Save.

75
CHAPTER 6. 内容结构 6.6. SETTING UP A TAXONOMY

5. You will receive a confirmation about the term you created. Add more terms. For example, ”Eggs” and
”Milk”.

76
CHAPTER 6. 内容结构 6.6. SETTING UP A TAXONOMY

6. In the Manage administrative menu, navigate to Structure > Content Types (admin/structure/types).
Click Manage fields for your Recipe content type.

7. Click Add field, and enter values from the table below. Click Save and continue.

Field name Explanation Value

Add a new field Select the field type Reference > Taxonomy term
Label The title to give the field Ingredients

8. On the following configuration screen, enter the values from the table below. Click Save field settings.

77
CHAPTER 6. 内容结构 6.6. SETTING UP A TAXONOMY

Field name Explanation Value

Type of item to reference The type of entity that is Taxonomy term
referenced by the field
Allowed number of values The number of values a user Unlimited
can enter

9. On the following configuration screen, enter the values from the table below. Click Save settings.

Field name Explanation Value

Help text Help shown to users creating Enter ingredients that site
content visitors might want to search
for
Reference type > Reference Select the method used to Default
method choose allowed values
Reference type > Available Select the vocabulary to Ingredients
Vocabularies choose allowed values from
Reference type > Create Whether new ingredient terms Checked
referenced entities if they don’ can be created from the
t already exist content editing form

78
CHAPTER 6. 内容结构 6.6. SETTING UP A TAXONOMY

10. Click Save settings. You will be taken back to the Manage Fields page. A message will be displayed saying
that the configuration for Ingredients is complete.

79
CHAPTER 6. 内容结构 6.7. ADDING A REFERENCE FIELD

Attributions
Written and edited by Bob Snodgrass, and Jojy Alphonso at Red Crackle.

6.7 Adding a Reference Field

Goal
Add a reference field so that recipes can be linked to the vendor that has submitted it.

Prerequisite knowledge
• Section 6.3, “Adding Basic Fields to a Content Type”

• Section 6.4, “Concept: Reference Fields”

• Section 6.1, “Adding a Content Type”

Site prerequisites
The Recipe and Vendor content types must exist. See Section 6.1, “Adding a Content Type”.

Steps
1. In the Manage administrative menu, navigate to Structure > Content types (admin/structure/types). Then
click Manage fields in the dropdown button for the Recipe content type. The Manage fields page appears.
2. Click Add field. The Add field page appears. Fill in the fields as shown below. Click Save and continue.

Field name Explanation Value

Add a new field Option to specify the field type Reference > Content
Label The title you want to give the Submitted by
field

80
CHAPTER 6. 内容结构 6.7. ADDING A REFERENCE FIELD

3. The page Submitted by appears which lets you set the allowed number of values. Fill in the fields as
shown below. Click Save field settings.

Field name Explanation Value

Type of item to reference Option to select the type of Content
referenced item
Allowed number of values Specify the count of values Limited, 1
associated with the field

4. The page Submitted by settings for Recipe appears which allows you to configure the field. Fill in the fields
as shown below. Click Save settings.

81
CHAPTER 6. 内容结构 6.7. ADDING A REFERENCE FIELD

Field name Explanation Value

Label Title shown for this field on Submitted by
the page
Help text Brief text aiding the person Choose the vendor that
creating content submitted this recipe
Required field Whether a value has to be Checked
provided or not
Reference method Option to select reference Default
method
Content types Specify the content type Vendor
Sort by Sorting field Title
Sort direction Sorting order Ascending

5. The Submitted by field has been added to the content type.

82
CHAPTER 6. 内容结构 6.8. CONCEPT: FORMS AND WIDGETS

Attributions
Written and edited by Boris Doesborg, and Jojy Alphonso at Red Crackle.

6.8 Concept: Forms and Widgets

Prerequisite knowledge
Section 2.3, “Concept: Content Entities and Fields”

What are forms and widgets?

The content management system software that your site is running allows administrators to edit content and
configure settings online, using various web forms. In particular, content editing forms are used to edit your site’
s content, and they are configurable by administrators; settings configuration forms are provided by modules
and cannot themselves be configured.
The data in your site’s content is stored in one or more fields that are attached to the content type and/or
sub-type. When you configure the content editing form for each content sub-type, you can:

• Select a widget for each field. A widget defines the method used to enter the data for the field. For
example, a taxonomy term can be chosen using an autocomplete field, a select list, or a tags-style field
that lets editors add new tags automatically.
• Configure widget settings. For example, you can choose the size of a plain-text entry field.
• Hide one or more fields from the editing form.

• Reorder the fields.

In principle, you can also have multiple content editing forms available for each content sub-type. This
feature is rarely used, however; the only exception in common use is for the user profile fields: you can use
different forms for user registration and user editing. For example, you might have a limited set of fields shown
when users first register on the site, and more fields shown later on when they edit their profiles.

83
CHAPTER 6. 内容结构 6.9. CHANGING CONTENT ENTRY FORMS

Related topics
• Section 6.9, “Changing Content Entry Forms”

• Section 6.10, “Concept: View Modes and Formatters”

Attributions
Written by Jennifer Hodgdon.

6.9 Changing Content Entry Forms

Goal
Change the Recipe form to use a different widget to enter terms in the Ingredients field.

Prerequisite knowledge
• Section 6.1, “Adding a Content Type”
• Section 6.3, “Adding Basic Fields to a Content Type”
• Section 6.5, “Concept: Taxonomy”
• Section 6.8, “Concept: Forms and Widgets”

Site prerequisites
The Recipe content type must exist, and it must have an Ingredients taxonomy term reference field. See
Section 6.1, “Adding a Content Type”and Section 6.6, “Setting Up a Taxonomy”.

Steps
1. In the Manage administrative menu, navigate to Content > Add content > Recipe (node/add/recipe) to
look at the content entry form that is set up by default. Notice how you have to enter ingredients one by
one, instead of having a more compact format.
2. In the Manage administrative menu, navigate to Structure > Content types (admin/structure/types). Then
click Manage form display on the dropdown button for the Recipe content type. The Manage form display
page appears.
3. For the Ingredients field, select Autocomplete (Tags style) in the Widget column.

84
CHAPTER 6. 内容结构 6.9. CHANGING CONTENT ENTRY FORMS

85
CHAPTER 6. 内容结构 6.9. CHANGING CONTENT ENTRY FORMS

4. Click Save.

5. In the Manage administrative menu, navigate to Content > Add content > Recipe (node/add/recipe) to
verify the changed behavior of the content form. The Ingredients field is now a single text field that
accepts multiple values.

6. Create two Recipe content items (see Section 5.2, “Creating a Content Item”), such as recipes for
”Green Salad” and ”Fresh Carrots”. Make sure all the fields have values, including images, ingredients,
and submitted by (set this to one of the Vendor content items you created in Section 6.3, “Adding Basic
Fields to a Content Type”).

Expand your understanding

Change the main site Contact form by navigating in the Manage administrative menu to Structure > Contact
forms. For instance, you may want to hide the Send yourself a copy or Language fields.
Attributions
Written by Boris Doesborg.

86
CHAPTER 6. 内容结构 6.10. CONCEPT: VIEW MODES AND …

6.10 Concept: View Modes and Formatters

Prerequisite knowledge
Section 6.1, “Adding a Content Type”

What is a View mode?

How an entity (such as content, a user or a comment) is displayed, depends on the context in which it is shown.
This context is known as a view mode. Examples of view modes are:
• a full page of the content with all the field values

• a teaser of the content with a thumbnail image and a Read more link
• a full user profile with a zoomable portrait photo
• a user avatar with username and a link to the profile
Every view mode can be configured through the administration pages. To see the configuration options
for the view modes of the Recipe content type, navigate in the Manage administrative menu to Structure >
Content types (admin/structure/types) and click Manage display from the dropdown button. In each view mode,
all fields can be hidden or displayed, and if they are displayed, you can choose and configure the field formatter.

What is a field formatter?

A field formatter is a setting for displaying the field values. For example, long text fields can be displayed
trimmed or full-length, and taxonomy term reference fields can be displayed in plain text or linked to the
taxonomy term page. Consult the Manage display page to see the field formatters for the fields of the Recipe
content type.

Related topics
• Section 6.1, “Adding a Content Type”
• Section 6.11, “Changing Content Display”

Additional resources
Drupal.org community documentation page ”View modes”
Attributions
Adapted by Boris Doesborg from ”View modes”, copyright 2000-2017 by the individual contributors to the
Drupal Community Documentation.

6.11 Changing Content Display

Goal
Make the content items more readable, accessible, and visibly attractive by reordering the fields, hiding labels,
and tuning the output of the fields.

Prerequisite knowledge
• Section 2.3, “Concept: Content Entities and Fields”
• Section 6.10, “Concept: View Modes and Formatters”

87
CHAPTER 6. 内容结构 6.11. CHANGING CONTENT DISPLAY

Site prerequisites
The Vendor content type must exist, it must have Main Image and Vendor URL fields, and your site must have
at least one Vendor content item. See Section 6.1, “Adding a Content Type”, Section 6.3, “Adding Basic
Fields to a Content Type”, and Section 5.2, “Creating a Content Item”.

Steps
1. Find and view a Vendor content item you created in Section 6.3, “Adding Basic Fields to a Content
Type”. Notice that there are several things that could be done to improve how the page looks:

• The Main Image and Vendor URL fields should not have labels.
• The order of the fields should be changed so that the image comes first.
• The image should be smaller.

2. To fix the first two problems, and update some additional settings, in the Manage administrative menu,
navigate to Structure > Content types (admin/structure/types). Then click Manage display in the drop-
down button for the Vendor content type.

3. Under the Label column, select Hidden for Main image. Do the same for Vendor URL.

88
CHAPTER 6. 内容结构 6.11. CHANGING CONTENT DISPLAY

4. Click the gear for the Vendor URL field. Clear the Trim link text length setting. Links will no longer have
a trim length. Check the Open link in new window checkbox. Now, when the link is clicked, it will open
in a new browser window. Click Update.

89
CHAPTER 6. 内容结构 6.11. CHANGING CONTENT DISPLAY

5. Drag the cross arrows next to the field items to reorder as Main image, Body, Vendor URL, and Links.

90
CHAPTER 6. 内容结构 6.12. CONCEPT: IMAGE STYLES

6. Click Save.

7. Find the Vendor content item from step 1 again, and verify that the updates have been made.
8. Repeat similar steps to manage the display of the Recipe content type fields.

Expand your understanding

• Make the main image smaller. See Section 6.13, “Setting Up an Image Style”.
• If you do not see the effect of these changes in your site, you might need to clear the cache. See Section 12.2,
“Clearing the Cache”.

Related concepts
Section 6.12, “Concept: Image Styles”

Additional resources
• Drupal.org community documentation page ”Specify how fields are displayed”
• Drupal.org community documentation page ”Rearrange the order of fields”

• Drupal.org community documentation page ”View modes”

Attributions
Written by Ann Greazel and Boris Doesborg.

6.12 Concept: Image Styles

Prerequisite knowledge
Section 6.3, “Adding Basic Fields to a Content Type”

91
CHAPTER 6. 内容结构 6.13. SETTING UP AN IMAGE STYLE

What are image styles?

Image styles allow you to upload a single image but display it in several ways; each display variation, or image
style, is the result of applying one or more effects to the original image.
As an example, you might upload a high-resolution image with a 4:3 aspect ratio, and display it scaled down,
square cropped, or black-and-white (or any combination of these effects). The core software provides a way to
do this efficiently:
1. Configure an image style with the desired effects on the Image styles page (admin/config/media/image-
styles).
2. The effects will be applied the first time a particular image is requested in that style.
3. The resulting image is saved.
4. The next time that same style is requested, the saved image is retrieved without the need to recalculate
the effects.
The core software provides several effects that you can use to define styles; others may be provided by
contributed modules.
Visit the Image styles page via the Manage administrative menu, navigate to Configuration > Media >
Image styles (admin/config/media/image-styles) to see the image styles that are defined by default.

Related topics
• Section 6.13, “Setting Up an Image Style”
• Section 6.14, “Concept: Responsive Image Styles”
• Section 6.3, “Adding Basic Fields to a Content Type”

Additional resources
Drupal.org community documentation page ”Working with images in Drupal 7 and 8”
Attributions
Adapted and edited by Boris Doesborg, and Jojy Alphonso at Red Crackle, from ”Working with images in
Drupal 7 and 8”, copyright 2000-2017 by the individual contributors to the Drupal Community Documentation

6.13 Setting Up an Image Style

Goal
Add an image style and use it to display images on Vendor pages.

Prerequisite knowledge
• Section 6.3, “Adding Basic Fields to a Content Type”
• Section 6.11, “Changing Content Display”
• Section 6.12, “Concept: Image Styles”

Site prerequisites
• Vendor and Recipe content types must exist. See Section 6.1, “Adding a Content Type”.
• Main image fields must exist for both content types. See Section 6.3, “Adding Basic Fields to a Content
Type”.
• Content items must exist for both content types. See Section 6.1,“Adding a Content Type”, Section 6.3,
“Adding Basic Fields to a Content Type”, and Section 5.2, “Creating a Content Item”.

92
CHAPTER 6. 内容结构 6.13. SETTING UP AN IMAGE STYLE

Steps
1. In the Manage administrative menu, navigate to Configuration > Media > Image styles (admin/config/media/image-
styles).
2. Click Add image style.
3. Enter the name Extra medium (300x200)
4. Click Create new style. The page Edit style Extra medium (300x200) appears.

5. In the Effect table, select Scale and crop. Click Add.

6. Fill in the fields as shown below.

Field name Value

Width 300
Height 200

7. Click Add effect. The image style is saved with the chosen effects.

93
CHAPTER 6. 内容结构 6.13. SETTING UP AN IMAGE STYLE

94
CHAPTER 6. 内容结构 6.13. SETTING UP AN IMAGE STYLE

8. In the Manage administrative menu, navigate to Structure > Content types (admin/structure/types).

9. Click Manage display in the Operations dropdown for the Vendor content type. The Manage display page
(admin/structure/types/manage/vendor/display) appears.
10. Ensure that the secondary tab Default is selected.
11. Click the cogwheel next to Main image for the configuration options.

12. Fill in the fields as shown below.

Field name Value

Image style Extra medium (300x200)
Link image to Nothing

13. Click Update.

14. Click Save. The new image style will be used while displaying Vendor content.

15. Open a Vendor content item and verify that it now shows up with the scaled-down image. See Section 5.3,
“Editing a Content Item”for information on how to locate an existing content item.
16. Repeat steps 8-15 for the Recipe content type.

Related concepts
• Section 6.3, “Adding Basic Fields to a Content Type”
• Section 6.12, “Concept: Image Styles”

• Section 6.14, “Concept: Responsive Image Styles”

95
CHAPTER 6. 内容结构 6.14. CONCEPT: RESPONSIVE IMAGE STYLES

Additional resources
Drupal.org community documentation page ”Working with images in Drupal 7 and 8”
Attributions
Adapted and edited by Boris Doesborg, and Jojy Alphonso at Red Crackle from ”Working with images in
Drupal 7 and 8”, copyright 2000-2017 by the individual contributors to the Drupal Community Documentation.

6.14 Concept: Responsive Image Styles

Prerequisite knowledge
• Section 1.3, “概念：主题”
• Section 6.11, “Changing Content Display”
• Section 6.12, “Concept: Image Styles”

What are responsive image styles?

The core Responsive Image module provides responsive image styles. This allows you to have images in your
website that are specifically sized for different screen sizes. This is useful, for example, to make your site load
faster on mobile devices because image sizes are optimized for smaller screens.
A responsive image style is a mapping between images styles and breakpoints. Breakpoints are the points
where a responsive design needs to change in order to respond to different screen sizes. Responsive image styles
can only be used if the breakpoints are defined in the theme.
When a responsive image style is defined, it can be used in the display settings for Image fields. This allows
the site to display responsive images using the HTML5 picture tag.

Related topics
Section 6.3, “Adding Basic Fields to a Content Type”

Additional resources
• Drupal.org community documentation page ”Responsive web design”

• Drupal.org community documentation page ”Responsive images in Drupal 8”

• Drupal.org community documentation page ”Working with breakpoints in Drupal 8”

Attributions
Adapted by Boris Doesborg from Responsive images in Drupal 8, copyright 2000-2017 by the individual
contributors to the Drupal Community Documentation.

6.15 Concept: Text Formats and Editors

What are text formats and filters?
Text formats change how HTML tags and other text are processed and displayed on your site. Text formats
are composed of a series of filters, each of which transforms text. When users create content, a text format is
associated with the content, and the full, original text is stored in the database. The content is then passed
through the filters in the text format before it becomes output on the site.
The core Filter module provides text format functionality, and the core Standard installation profile sets up
Basic HTML, Restricted HTML, and Full HTML text formats. Each text format has an associated permission,
so that you can allow only trusted users to use permissive text formats. This restricts untrusted users to text
formats like Basic HTML, which filters out dangerous HTML tags.

96
CHAPTER 6. 内容结构 6.16. CONFIGURING TEXT FORMATS AND …

What are the editors associated with text formats?

Each text format can be associated with an editor, such as a visual WYSIWYG (What You See Is What You
Get) HTML editor. The core Text Editor module provides the ability to associate editors with text formats,
and to configure the editors (such as adding and removing buttons from their toolbars). The core CKEditor
module provides the industry-standard editor known as CKEditor, so that it can be used to edit HTML content
on your site.

What is cross-site scripting?

Cross-site scripting (XSS) is a security vulnerability typically found in websites. In a site that is not well
protected, malicious users can enter script into web pages that are viewed by other users (for example, in a
comment or in the body of a page). A cross-site scripting vulnerability may be used by attackers to login as
another user. It is important to configure the text formats of your website to prevent such abuse.

Related topics
Section 13.3, “Concept: Security and Regular Updates”

Additional resources
• Drupal.org community documentation page ”Filter module: text formats that filter user input”
• Wikipedia page ”Cross-site scripting”

Attributions
Written and edited by Boris Doesborg and Jennifer Hodgdon.

6.16 Configuring Text Formats and Editors

Goal
Add a horizontal rule tag to the Basic HTML text format, and a corresponding button to its editor configuration.

Prerequisite knowledge
Section 6.15, “Concept: Text Formats and Editors”

Site prerequisites
• The core Filter, Editor, and CKEditor modules must be installed. They are installed on your site when
you install with the core Standard installation profile.

• The Basic HTML text format must exist. This is created on your site when you install with the core
Standard installation profile.

Steps
1. In the Manage administrative menu, navigate to Configuration > Content authoring > Text formats and
editors (admin/config/content/formats). The Text formats and editors page appears.
2. Click Configure for the Basic HTML text format. The Basic HTML page appears.
3. Note that CKEditor is selected in the Text editor field. This allows you to configure the editor’s toolbar.

97
 CHAPTER 6. 内容结构 6.16. CONFIGURING TEXT FORMATS AND …

4. Drag the horizontal rule button from Available buttons to Tools in Active toolbar. You may need to click
the Show group names link to see the Tools group name.

5. Note that you can change the Filter processing order.

6. In the field Allowed HTML tags, add <hr> to what is already present.

7. Click Save configuration. You will be taken back to the Text formats and editors page. A message will be
displayed saying that the text format has been updated.

Expand your understanding

If you do not see the effect of these changes in your site, you might need to clear the cache. See Section 12.2,
“Clearing the Cache”.
Attributions
Written by Boris Doesborg.

98
Chapter 7

管理用户账号

7.1 概念：用户，角色和权限
什么是用户？
访问网站的任何人都是用户，包括您自己。有三类用户：

• 未登录用户，或匿名用户
• 已登录用户
• 安装网站时自动创建的管理员账号，或用户 1。请查看 Section 7.2, “Concept: The User 1 Account”。

什么是权限？
权限决定用户是否能够在网站上执行操作（包括浏览内容，编辑内容，以及改变配置）。每个权限都有一个名
字 (比如：查看已发布内容) ，它控制一个操作或者多个操作。用户必须被授予权限才能在站点上执行相应的操
作。权限由提供操作的模块定义。

什么是角色？
不同于直接为每个用户单独分配权限，角色包含一组权限. 您可以在网站上定义一个或更多角色, 然后分配不同
的权限给不同的角色。授予给已登录用户和匿名用户的权限分别包含在已登录用户角色和匿名用户角色中。取
决于您在安装站点时选择的安装类型，可能会创建有一个叫管理员的角色。这个角色拥有所有的权限。
每个账号会自动获得已登录用户角色，同时，每个账号可以拥有一个或多个其他角色。当将角色分配给账
号后，该账号对应的用户在登录时将拥有该角色拥有的所有权限。
创建多个角色是一种好的实践。以农贸市场站点为例，可能需要以下角色：
• 供应商角色，允许供应商编辑自己的供应商列表页面

• 内容编辑角色，用于编辑一般农贸市场页面
• 用户管理员角色，用于管理供应商帐户
• 管理员角色，安装网站时自动创建，供高级用户管理站点配置

相关话题
• Section 7.3, “Creating a Role”
• Section 7.5, “Assigning Permissions to a Role”

• Section 7.6, “Changing a User’s Roles”

• Section 7.4, “Creating a User Account”

99
CHAPTER 7. 管理用户账号 7.2. CONCEPT: THE USER 1 ACCOUNT

• Section 7.2, “Concept: The User 1 Account”

• Section 7.7, “Assigning Authors to Content”

相关资料
• Drupal 官网文档：用户，角色和权限

• Drupal 官网文档：管理用户
• Drupal 官网文档：用户角色

贡献者
编写：Mark LaCroix，Boris Doesborg，和 Jennifer Hodgdon 改编自 用户角色，© 2000-2017 Drupal 社区
文档贡献者
翻译：冉强军 @ InterGreat Education Group，qingguo

7.2 Concept: The User 1 Account

Prerequisite knowledge
Section 7.1, “概念：用户，角色和权限”

What is the user 1 account?

During the installation of your site, you created the first user account. Each user account internally has a
numeric user ID, and since the ID of this user is one, it is commonly referred to as the user 1 account. This user
account is special, because independent of what roles it is assigned, someone logged in as user 1 has permission
to do all actions on the site, including viewing and editing all content, editing any user account, changing site
configuration, installing and uninstalling modules, and running the update script.
Because of this level of permission, some people refer to this account as the root user, similar to the ”root”
user account that has full administrative permissions in Linux and other operating systems.
It is usually better to make separate accounts for each administrative user, giving them the Administrator
role, rather than having all administrative users log in using the user 1 account. There are several reasons for
this:
• Some actions and updates on the site are logged, and if everyone uses the same account, it is difficult to
know who did them if you have questions.

• The Administrator role permissions can be modified to be safer than the full permissions of the user 1
account, so that people do not inadvertently change site features that shouldn’t be changed.
• People’s responsibilities on a site may change over time. With ordinary user accounts, this can be
mirrored in permissions by assigning or unassigning roles to their user accounts. If they are all using the
user 1 account, this is more difficult.

• On some sites, the author of content or comments is displayed or tracked, and if everyone uses the same
account to create content, it is difficult to know who created the content.
It is not possible to delete the user 1 account from the administrative user interface. It would be possible
to do with a database query, but it could cause problems in your site and is not advisable.

Additional resources
Drupal.org community documentation page ”Accounts and roles”
Attributions
Written and edited by Mark LaCroix and Jennifer Hodgdon.

100
CHAPTER 7. 管理用户账号 7.3. CREATING A ROLE

7.3 Creating a Role

Goal
Create a Vendor role to allow some - but not all - users to perform specific tasks.

Prerequisite knowledge
Section 7.1, “概念：用户，角色和权限”

Steps
1. In the Manage administrative menu, navigate to People > Roles (admin/people/roles).
2. You will find default roles Anonymous user, Authenticated user, and Administrator already present.

101
CHAPTER 7. 管理用户账号 7.3. CREATING A ROLE

3. Click Add Role to add a custom role.

102
CHAPTER 7. 管理用户账号 7.4. CREATING A USER ACCOUNT

4. Type Vendor in the Role name field. Click Save.

5. You will see the message ”Role Vendor has been added.” displayed at the top of the page.

Expand your understanding

• Section 7.5, “Assigning Permissions to a Role”

• Section 7.6, “Changing a User’s Roles”

Additional resources
Drupal.org community documentation page ”User Roles”
Attributions
Adapted and edited by Jack Probst, Boris Doesborg, and Joe Shindelar from ”User Roles”, copyright 2000-
2017 by the individual contributors to the Drupal Community Documentation

7.4 Creating a User Account

Goal
Create Vendor user accounts for Sweet Honey and Happy Farm vendors.

Prerequisite knowledge
• Section 7.1, “概念：用户，角色和权限”
• Section 7.2, “Concept: The User 1 Account”
• Section 7.3, “Creating a Role”

103
CHAPTER 7. 管理用户账号 7.4. CREATING A USER ACCOUNT

Site prerequisites
The Vendor role must exist on your site. See Section 7.3, “Creating a Role”.

Steps
1. In the Manage administrative menu, navigate to People (admin/people).
2. Click Add user.

3. Fill in the form fields. See the table below.

104
CHAPTER 7. 管理用户账号 7.4. CREATING A USER ACCOUNT

Field name Explanation Example value

Email address A valid email address for the [email protected]
vendor. All emails from the
system will be sent to this
address. The email address is
not made public.
Username A username for the vendor Sweet Honey
that they will use to sign in or
author content items. Spaces
are allowed; punctuation is not
allowed except for periods,
hyphens, apostrophes, and
underscores.
Password A password the vendor will use (Make a secure password)
to sign in to the site. You can
see how safe the password is on
the Password strength gauge.
You also get tips on how to
make it safer.
Confirm password Type the same password to (Repeat password)
avoid any typing mistakes.
Status Set the status of the user Active
account. Blocked users will not
be able to sign in.
Roles Set the role of the user Vendor
account.
Notify user of new account Whether or not to send a Checked
notification to the vendor’s
email address.
Picture Click Browse and select a Photo of the vendor
picture to upload. Pay
attention to size restrictions.
Contact settings Enable or disable the display of Checked
a contact form for the account.

4. Click Create new account. You will get a notification about the user account creation.

5. Create a second Vendor account for Happy Farm by following the steps above.

Expand your understanding

Create a user account for yourself.
Attributions
Written by Diána Lakatos at Pronovix.

105
CHAPTER 7. 管理用户账号 7.5. ASSIGNING PERMISSIONS TO A ROLE

7.5 Assigning Permissions to a Role

Goal
Change the permissions for the Vendor role so that users can create, edit, and delete Recipe and Vendor content,
format the content, and contact each other.

Prerequisite knowledge
• Section 7.1, “概念：用户，角色和权限”

Site prerequisites
The Vendor role must exist on your site. See Section 7.3, “Creating a Role”.

Steps
1. In the Manage administrative menu, navigate to People > Roles (admin/people/roles). The Roles page
appears.
2. Click Edit permissions in the dropdown for the Vendor role. The Edit role page appears where you can
see all the available actions for the website such as, for example, Post comments or Administer blocks.
The available permissions depend on the modules that are installed in the site. Note: Some permissions
may have security implications. Be cautious while assigning permissions to roles.

3. Check the boxes for the following permissions, listed by module:

Module Permission
Contact Use users’ personal contact forms
Filter Use the Restricted HTML text format
Node Recipe: Create new content
Node Recipe: Edit own content
Node Recipe: Delete own content
Node Vendor: Edit own content
Quick Edit Access in-place editing

106
CHAPTER 7. 管理用户账号 7.5. ASSIGNING PERMISSIONS TO A ROLE

4. Click Save permissions. You will get a message saying your changes have been saved.

Expand your understanding

• Log in as one of the new users you created in Section 7.4, “Creating a User Account”. Verify whether
you have the correct permissions.
• Section 7.6, “Changing a User’s Roles”

107
 CHAPTER 7. 管理用户账号 7.6. CHANGING A USER’S ROLES

Related concepts
Section 7.2, “Concept: The User 1 Account”

Additional resources
Drupal.org community documentation page ”Managing Users”
Attributions
Adapted and edited by Boris Doesborg, Brian Emery, and Jojy Alphonso at Red Crackle, from ”User Roles”,
copyright 2000-2017 by the individual contributors to the Drupal Community Documentation.

7.6 Changing a User’s Roles

Goal
Change or add roles to a given user, either by editing a single-user or by applying a bulk operation.

Prerequisite knowledge
Section 7.1, “概念：用户，角色和权限”

Site prerequisites
The user account that you want to update, and the role you want it to have, must already exist. See Section 7.4,
“Creating a User Account”, Section 7.3, “Creating a Role”, and Section 7.5, “Assigning Permissions to a
Role”.

Steps
Updating the roles using single-user editing method
1. In the Manage administrative menu, navigate to People (admin/people).
2. Locate the user 1 account (named ”admin”) to assign it the Administrator role. If it is not immediately
visible, use the Name or email contains filter, or other filters, to narrow down the list.
3. Click Edit to update the user account.

108
CHAPTER 7. 管理用户账号 7.6. CHANGING A USER’S ROLES

4. On the Edit page, scroll down to Roles section. Check the Administrator role for the user account.

5. Click Save to update the user account. You should be returned to the People page and see a message
saying that the changes have been saved.

Updating the roles using bulk editing method

1. If the users Happy Farm and Sweet Honey did not already have the Vendor role, here is how you would
add it. In the Manage administrative menu, navigate to People (admin/people).
2. Locate Vendor user accounts Sweet Honey and Happy Farm and check them. If they are not immediately
visible, use the Name or email contains filter, or other filters, to narrow down the list.

109
CHAPTER 7. 管理用户账号 7.7. ASSIGNING AUTHORS TO CONTENT

3. Select Add the Vendor role to the selected users from the Action select list.

4. Click Apply to selected items. You should see a message indicating that the desired changes were made.

Attributions
Written by Chris Dart and Jennifer Hodgdon

7.7 Assigning Authors to Content

Goal
Assign Vendor content items Happy Farm and Sweet Honey to the corresponding Vendor user accounts, so they
can edit their own Vendor profiles on the site.

Prerequisite knowledge
• Section 7.1, “概念：用户，角色和权限”

Site prerequisites
• The Vendor content type must exist, and your site must have at least two Vendor content items. See
Section 6.1, “Adding a Content Type”, Section 6.3, “Adding Basic Fields to a Content Type”, and
Section 5.2, “Creating a Content Item”.
• User accounts for at least two vendors must exist. See Section 7.4, “Creating a User Account”.

Steps
1. In the Manage administrative menu, navigate to Content (admin/content).
2. Find Vendor content item Happy Farm in the list. If it is not immediately visible, you can filter the list
by Published status, Content type (Vendor), Title, or Language. Click Edit for the Vendor content item
you would like to assign an author to.

3. Locate the information block and click Authoring information.

110
CHAPTER 7. 管理用户账号 7.7. ASSIGNING AUTHORS TO CONTENT

4. Start typing the Vendor’s user name Happy Farm in the Authored by field. The field lists matching user
names. Select the Vendor’s user name from the list.
5. Click Save and keep published.
6. You will get a notification that the Vendor content item has been updated.

7. Follow these steps again to assign Vendor content item Sweet Honey to the Vendor user account Sweet
Honey.

Attributions
Written by Diána Lakatos at Pronovix.

111
 Chapter 8

区块

8.1 Concept: Blocks

What is a block?
Blocks are individual pieces of your site’s web page layout. They are placed inside the regions (see Section 2.1,
“Concept: Regions in a Theme”) of your theme, and can be created, removed, and rearranged in the Block
layout (admin/structure/block) administration page. Examples of blocks include the Who’s online listing, the
main navigation menu, and the breadcrumb trail. The main page content is also a block.
Some modules make new blocks available for placement on your site. For example, when the core Search
module is installed and configured, it provides a block that contains a search form. You may also create and
place your own custom blocks.
Each block has its own configuration settings, which allow you to select which pages of your site will display
the block. It is even possible to place multiple copies of a block, each with its own separate configuration and
visibility rules.

Related topics
• Section 2.1, “Concept: Regions in a Theme”
• Section 8.2, “Creating A Custom Block”
• Section 8.3, “Placing a Block in a Region”

Attributions
Adapted by Les Lim from ”Working with blocks (content in regions)” copyright 2000-2017 by the individual
contributors to the Drupal Community Documentation.

8.2 Creating A Custom Block

Goal
Create a block showing the hours and location of the farmers market.

Prerequisite knowledge
• Section 8.1, “Concept: Blocks”

• Section 2.1, “Concept: Regions in a Theme”

113
CHAPTER 8. 区块 8.2. CREATING A CUSTOM BLOCK

Steps
1. In the Manage administrative menu, navigate to Structure > Block layout > Custom block library (admin/structure/block/
content).
2. Click Add custom block. The Add custom block page appears.
3. Fill in the fields as shown below.

Field name Explanation Example value

Block description Name of the block shown to Hours and location block
administrators
Body Content of the block when it is Open: Sundays, 9 AM to 2
displayed PM, April to September<br
/>Location: Parking lot of
Trust Bank, 1st & Union,
downtown Anytown.

4. Click Save. A message appears indicating the block has been saved.

114
CHAPTER 8. 区块 8.3. PLACING A BLOCK IN A REGION

Expand your understanding

• Edit the content of your custom block. In the Manage administrative menu, navigate to Structure > Block
layout > Custom block library (admin/structure/block/block-content). Find your block in the list and click
Edit to make changes.
• Place the block you created in the sidebar. See Section 8.3, “Placing a Block in a Region”for details.

Additional resources
Drupal.org community documentation page ”Working with blocks (content in regions)”
Attributions
Adapted by Jacob Redding and Boris Doesborg from Working with blocks (content in regions), copyright
2000-2017 by the individual contributors to the Drupal Community Documentation.

8.3 Placing a Block in a Region

Goal
Place the Opening hours and location block in the website’s sidebar.

Prerequisite knowledge
Section 8.1, “Concept: Blocks”

Site prerequisites
• The core Bartik theme must be installed and set as default. See Section 4.6, “Configuring the Theme”.
• The Opening hours and location block must exist. See Section 8.2, “Creating A Custom Block”.

Steps
1. In the Manage administrative menu, navigate to Structure > Block layout (admin/structure/block). The
Block layout page appears, listing the theme’s regions.

2. Ensure that in the secondary tab the core Bartik theme is selected. Block placement is defined per theme.
3. Locate the region Sidebar second in the list and click Place block next to it. The Place block window
appears, listing all the blocks.
4. Locate the block Opening hours and location and click Place block next to it. The Configure block window
appears. Fill in the fields as shown below.

Field name Value

Title Hours and location
Display title Checked
Region Sidebar second

You can also hide or display the block on specific pages. In the case of the Farmer’s market website you
do not set any of these configuration options because you want to show the block everywhere.

115
CHAPTER 8. 区块 8.3. PLACING A BLOCK IN A REGION

5. Click Save block. The Block layout page appears. You can drag blocks to change the order in which they
will appear.
6. Verify that the Opening hours and location block is listed in the Sidebar second region, and click Save
blocks.
The block has been placed on the sidebar of all pages that use the core Bartik theme.

116
CHAPTER 8. 区块 8.3. PLACING A BLOCK IN A REGION

Expand your understanding

• Remove the Powered by Drupal block from the Footer fifth region by setting the region to - None -.
• Remove the Tools block from the Sidebar first region by setting the region to - None -. This block is only
visible to logged-in users.
• Place the User login block in a region.

• If you do not see the effect of these changes in your site, you might need to clear the cache. See Section 12.2,
“Clearing the Cache”.

Attributions
Written and edited by Boris Doesborg and Jennifer Hodgdon.

117
Chapter 9

用视图创建列表

9.1 Concept: Uses of Views

Prerequisite knowledge
• Section 2.4, “Concept: Modular Content”
• Section 2.3, “Concept: Content Entities and Fields”

What is a view?
A view is a listing of content on a website. The core Views module handles the display of views, and the core
Views UI module allows you to create and edit them in the administrative interface. When you define views,
you are interested in taking data from your website and displaying it to the user.

What types of data can be displayed using views?

You can create views to output practically any content entity that is stored in the system. For example, you
can create the following lists for the farmers market site:
• Lists of vendors
• Lists of recipes
• Lists of the most recent content on the site
• Lists of users on the site

What are the ways data can be output using views?

A listing created by a view can be in any of the following forms:
• Table with sortable fields
• Grid layouts
• Teasers or pictures that link to articles
• Blocks
• JSON output
• RSS feeds
• Calendars
• On-screen slideshows

119
CHAPTER 9. 用视图创建列表 9.2. 概念：视图的组成

Related topics
• Section 9.2, “概念：视图的组成”

• Section 9.3, “Creating a Content List View”

Attributions
Written and edited by Michael Lenahan at erdfisch, and Jojy Alphonso at Red Crackle.

9.2 概念：视图的组成
预备知识
• Section 2.3, “Concept: Content Entities and Fields”
• Section 2.4, “Concept: Modular Content”
• Section 9.1, “Concept: Uses of Views”
• Section 5.1, “Concept: Paths, Aliases, and URLs”

• Section 8.1, “Concept: Blocks”

视图由哪些部分组成？
在管理界面中编辑视图时，将会看到以下部分：它们允许您指定输出的数据是什么，输出的顺序是什么，以及
输出的格式是什么：
显示 每个视图可以有一个或多个显示，每个显示可以产生一种类型的输出。显示类型包括：
页面 在一个特定的 URL 输出，并使其成为该 URL 的主要页面内容。
区块 在一个区块中输出，这个区块可以被放置到页面。
订阅源 创建一个 RSS 或者其他类型的订阅源。
附加 让输出可以附加到其他的显示。
格式 取决于显示类型，您可以选择以表格、网格、HTML 列表格式或其他格式显示您的数据。一些格式还给
您一个第二选择，让您选择是输出渲染后的实体还是字段。一些格式则不会给您这种选择（比如，如果
您使用表格格式，您只能使用字段）。
字段 取决于您选择的格式，您可能可以选择输出哪些内容字段。例如，如果您正在制作一个食谱内容条目的
视图，在一个区块显示中，您可能只显示食谱的食谱的名称，而在全文页面，拥有更多的空间，您可能
还会显示一个图像字段。

过滤条件 过滤器限制要输出的数据，基于条件，比如内容是否已发布，内容的类型或字段的值。例如，创建
一个食谱内容的视图，您可能需要过滤出食谱内容类型和已发布的食谱。过滤器还可以提供给用户，这
意味着用户将有一个表单，用户可以自行选择过滤器的值。您可以在一个“食谱”页面，让用户通过指定
的成分过滤出食谱。
排序标准 定义显示输出的顺序，可以基于任何内容字段。

上下文过滤器 上下文过滤器与常规过滤器类似，只是值来自所该视图显示的上下文，例如，页面显示时，页
面的完整 URL，当前日期或时间，或可以通过视图计算来检测到的其他值。
关联 关联允许通过所显示的基本内容与其他的内容实体建立关系，来扩展视图中显示的内容。关联使用涉及
到其他内容的基本内容的字段创建；一个例子是所有常规内容都有作者字段，它引用的是内容作者的账
号。一旦创建了一个关联，您就可以在视图中显示来自其所引用实体中的字段。

120
CHAPTER 9. 用视图创建列表 9.3. CREATING A CONTENT LIST VIEW

相关主题
Section 9.3, “Creating a Content List View”
贡献者
编写：Surendra Mohan 和 Jennifer Hodgdon
翻译：冉强军 @ InterGreat Education Group

9.3 Creating a Content List View

Goal
Create a page listing vendors that will be automatically updated whenever a vendor is added, deleted, or
updated on the site.

Prerequisite knowledge
• Section 9.1, “Concept: Uses of Views”
• Section 9.2, “概念：视图的组成”

Site prerequisites
• The core Views and Views UI modules must be installed. These are installed for you when you install
with the core Standard installation profile.

• The Vendor content type must exist, with URL and Main image fields. Your site must have a couple of
Vendor content items. See Section 6.1, “Adding a Content Type”, Section 6.3, “Adding Basic Fields
to a Content Type”, and Section 5.2, “Creating a Content Item”.
• The Medium (220x220) image style must be defined. This is created on your site when you install the
core Image module (installed with the core Standard installation profile) but can be recreated if deleted.
See Section 6.13, “Setting Up an Image Style”.

Steps
1. In the Manage administrative menu, navigate to Structure > Views > Add view (admin/structure/views/add).
The Add view wizard appears.
2. Fill in the fields as shown below.

Field name Explanation Example value

View name Name of the view that will be Vendors
visible in the administration
pages
Show Type of information listed in Content
the view
of type Specify content type Vendor
sorted by List order Title
Create a page Create a page that displays the Checked
view
Page title Title show above the view Vendors
Path Address of the page vendors
Display format Type of list Table
Items to display Number of items visible on the 10
page
Use a pager Split up the list in several Checked
pages if there are more items

121
CHAPTER 9. 用视图创建列表 9.3. CREATING A CONTENT LIST VIEW

Field name Explanation Example value

Create a menu link Add the view page to the menu Checked
Menu Menu in which to add the link Main navigation
Link text Label of the link in the menu Vendors

122
CHAPTER 9. 用视图创建列表 9.3. CREATING A CONTENT LIST VIEW

3. Click Save and edit. The view configuration page appears.

4. Click Add from the dropdown button in the Fields section. The Add fields pop-up appears.

123
CHAPTER 9. 用视图创建列表 9.3. CREATING A CONTENT LIST VIEW

5. Enter the word ”image” in the search field.

6. Check Main image in the table.

7. Click Apply. The Configure field: Content: Main Image pop-up appears.
8. Fill in the fields as shown below.

Field name Explanation Example value

Create a label Add a label before the field Unchecked
value
Image style The format of the image Medium (220x220)
Link image to Add a link to the content item Content

9. Click Apply. The view configuration page appears.

10. Click Add from the dropdown button in the Fields section. The Add fields pop-up appears.
11. Enter the word ”body” in the search field.

12. Select Body in the table.

13. Click Apply. The Configure field: Content: Body pop-up appears.
14. Fill in the fields as shown below.

Field name Explanation Example value

Create a label Add a label before the field Unchecked
value
Formatter The presentation of the field Summary or trimmed
value
Trimmed limit: The number of maximum 120
characters shown

15. Click Apply. The view configuration page appears.

16. Click Content: Title (Title) in the Fields list. The Configure field: Content: Title pop-up appears.
17. Uncheck Create a label. This will remove the label that was created by the wizard.
18. Click Apply. The view configuration page appears.

19. Click Rearrange from the dropdown button in the Fields section. The Rearrange fields pop-up appears.
20. Drag the fields into the right order: Image, Title. Body.
21. Click Apply. The view configuration page appears.
22. Optionally, click Update preview for a preview.

23. Click Save.

124
CHAPTER 9. 用视图创建列表 9.3. CREATING A CONTENT LIST VIEW

24. Navigate to the homepage and click Vendors from the main navigation to see the result.

125
CHAPTER 9. 用视图创建列表 9.4. DUPLICATING A VIEW

Expand your understanding

The link to the view in the main navigation will probably not be in the right place. Change the order of the
menu items in the main navigation. See Section 5.8, “Changing the Order of Navigation”.
Attributions
Written/edited by Boris Doesborg and Jennifer Hodgdon.

9.4 Duplicating a View

Goal
Create a page listing recipes by duplicating the existing Vendors view. Modify the page so that the recipes are
displayed in a grid and can by filtered by ingredients.

Prerequisite knowledge
• Section 9.1, “Concept: Uses of Views”
• Section 9.2, “概念：视图的组成”
• Section 9.3, “Creating a Content List View”

126
CHAPTER 9. 用视图创建列表 9.4. DUPLICATING A VIEW

Site prerequisites
• The Vendor and Recipe content types must exist; both must have Main image fields, and the Recipe
content type must have an Ingredients field. Your site must also have a couple of Recipe content items.
See Section 6.1, “Adding a Content Type”, Section 6.3, “Adding Basic Fields to a Content Type”,
Section 6.6,“Setting Up a Taxonomy”, Section 6.9,“Changing Content Entry Forms”, and Section 5.2,
“Creating a Content Item”.
• The Vendors view must exist. See Section 9.3, “Creating a Content List View”.

Steps
1. In the Manage administrative menu, navigate to Structure > Views (admin/structure/views). Find the
view ”Vendors” and click Duplicate in its dropdown button.

2. Name the duplicate ”Recipes” and click Duplicate. The view configuration page appears.
3. Change the title of the view page to ”Recipes” by clicking Vendors in the Title section. The Page: The
title of this view pop-up appears. Type in ”Recipes”. Click Apply.

127
CHAPTER 9. 用视图创建列表 9.4. DUPLICATING A VIEW

4. Change from a table to a grid format by clicking Table in the Format section. The Page: How should this
view be styled pop-up appears. Check Grid and click Apply. The Page: Style options pop-up appears.
Retain the default values and click Apply.
5. Retain only the title and image fields for the Recipes view by clicking Content: Body in the Fields section.
Click Remove in the pop-up that appears.
6. Change the content type filter to use the Recipe content type by clicking Content: Type (=Vendor) in the
Filter criteria section. In the Configure filter criterion: Content: Type pop-up, check Recipe and uncheck
Vendor. Click Apply.
7. Add a further filter that is exposed to visitors by clicking Add in the Filter criteria section. Search for
”ingredients” and check ”Ingredients (field_ingredients)”. Click Add and configure filter criteria.
8. The appearing pop-up offers extra settings on vocabulary and selection type. Click Apply and continue.
The next pop-up allows you to expose this filter to visitors. Fill in the fields as shown below, and click
Apply.

Field name Explanation Example value

Expose this filter to visitors, to Allow visitors to filter and Checked
allow them to change it search
Required Whether a value has to be Unchecked
provided or not
Label Label shown for this filter on Find recipes using…
the view page

128
CHAPTER 9. 用视图创建列表 9.4. DUPLICATING A VIEW

9. Change the Path label field to ”Recipes” by clicking ”/vendors” in the Page settings section. In the pop-up
that appears, enter the path ”recipes” and click Apply.
Note that when editing a view, you enter paths without the leading ”/”, unlike on other administrative
pages (such as when providing a path to a content item page).
10. Change the menu link title by clicking ”Normal: Vendors” in the Page settings section. In the pop-up
that appears, change the title to ”Recipes” and click Apply.

129
CHAPTER 9. 用视图创建列表 9.4. DUPLICATING A VIEW

11. In order to use Ajax (see Ajax entry in the Glossary) to make filtering and paging faster for users, click
Advanced to expand the section for more options. In the Other section, change Use AJAX: No to ”Yes”
by clicking No and checking Use AJAX in the pop-up that appears. Click Apply.
12. Click Save to save the view.
13. Go back to the home page and click Recipes in the navigation to view the new Recipes page.

Expand your understanding

The link to the view in the main navigation will probably not be in the right place. Change the order of the
menu items in the main navigation. See Section 5.8, “Changing the Order of Navigation”.

Related concepts
• Section 2.5, “Planning your Content Structure”
• Ajax entry in the Glossary

Attributions
Written and edited by Laura Vass at Pronovix, and Jojy Alphonso at Red Crackle.

130
CHAPTER 9. 用视图创建列表 9.5. ADDING A BLOCK DISPLAY TO A VIEW

9.5 Adding a Block Display to a View

Goal
Add a block display to the Recipes view to display the most recent recipes in a sidebar, and change its config-
uration without changing the existing Recipes page view.

Prerequisite knowledge
• Section 9.1, “Concept: Uses of Views”
• Section 9.2, “概念：视图的组成”
• Section 9.3, “Creating a Content List View”

Site prerequisites
• The Recipe content type must exist, it must have a Main image field, and your site must have a couple of
Recipe content items. See Section 6.1, “Adding a Content Type”, Section 6.3, “Adding Basic Fields
to a Content Type”, Section 6.9, “Changing Content Entry Forms”, and Section 5.2, “Creating a
Content Item”.
• The Thumbnail (100x100) image style must be defined. This is created on your site when you install the
core Image module (installed with the core Standard installation profile) but can be recreated if deleted.
See Section 6.13, “Setting Up an Image Style”.
• The Recipes view must exist. See Section 9.3, “Creating a Content List View”and Section 9.4, “Du-
plicating a View”.

Steps
1. In the Manage administrative menu, navigate to Structure > Views (admin/structure/views). Find the
view ”Recipes” and click Edit from its dropdown button. Alternatively, navigate to the Recipes page
in the main site navigation, and click the Edit view contextual link in the main area of the page. See
Section 4.1, “Concept: Administrative Overview”for information about contextual links.
2. Create a new block display by clicking Add in the Displays section. Click Block from the dropdown button.
The new display is created, and the focus is automatically switched to its configuration.

3. Change the title of this display by clicking Block next to Display name. The Block: The name and the
description of this display pop-up appears. Change the Administrative name to ”Recent recipes”. Click
Apply.

131
CHAPTER 9. 用视图创建列表 9.5. ADDING A BLOCK DISPLAY TO A VIEW

4. Change the title of the view by clicking Title: Recipes in the Title section. In the pop-up that appears,
select This block (override) from the For select list. Change the title to ”New recipes” and click Apply
(this display).

5. Change the view’s style by clicking Format: Grid in the Format section. In the pop-up that appears,
select This block (override) from the For select list. Select Unformatted list and Click Apply (this display).
You can further configure the style options in the next pop-up that appears. Then click Apply.
6. Configure the image field by clicking Content: Main image in the Fields section. In the pop-up that
appears, select This block (override) from the For select list. Select Image style Thumbnail (100x100).
Click Apply (this display).

132
CHAPTER 9. 用视图创建列表 9.5. ADDING A BLOCK DISPLAY TO A VIEW

7. Remove ingredients as a filter by clicking Content: Ingredients (exposed) in the Filter criteria section.
In the pop-up that appears, select This block (override) from the For select list. Click Remove at the
bottom.

8. Configure how you want the content to be sorted in the view by clicking Add in the Sort criteria section.
In the pop-up that appears, select This block (override) from the For select list. Check the field Authored
on (from Content category), and then Add and configure sort criteria.
9. In the appearing configuration pop-up, select Sort descending to have the most recent recipes appear first.
Click Apply.

10. Specify the number of items to be displayed by clicking Use pager: Mini in the Pager section. In the
pop-up that appears, select This block (override) from the For select list. Under Pager, select Display a
specified number of items. Click Apply (this display). In the Block: Pager options pop-up, provide ”5” as
the value for Items to display. Click Apply.

11. Click Save. You will either see the view editing page again, or the Recipes page, depending on what you
did in step 1. You should also see a message saying that the view has been saved.

133
CHAPTER 9. 用视图创建列表 9.5. ADDING A BLOCK DISPLAY TO A VIEW

12. Place the ”Recipes: Recent Recipes” block in the Sidebar second region. See Section 8.3, “Placing a
Block in a Region”. Navigate to the site’s home page to see the block.

Attributions
Written and edited by Laura Vass at Pronovix, Jennifer Hodgdon, and Jojy Alphonso at Red Crackle.

134
Chapter 10

多语言

10.1 Concept: User Interface, Configuration, and Content transla-

tion
Prerequisite knowledge
• Section 1.5, “Concept: Types of Data”
• Section 1.2, “概念：模块”
• Section 2.3, “Concept: Content Entities and Fields”

What can be translated on your site?

The base language for the software that your site runs (core software, modules, and theme) is English. However,
you can create either a site that displays in a different language or a multi-lingual site; if you do so, all relevant
text, images, and file attachments should be shown in the appropriate language for each site visitor. You need
to have the core Language module installed in order to use a language other than English on the site.
There are three types of information that you can translate, each with its own method for translating:
User interface text Built-in text present in the core software, modules, and themes. This can be translated
from the base English language of the software into the language(s) of your site. Typically, rather than
needing to translate this text yourself, you can download translations. You need to have the core Interface
Translation module installed in order to translate this text.
Configuration text Text whose structure and initial values are defined by the core software, modules, and
theme, but that you can edit. Examples include the labels for fields in your content types, header text
in views, your site name, and the content of automatic email messages that your site sends out. After
creating configuration text in the default language of your site, you can translate it into other languages.
You need to have the core Configuration Translation module installed in order to translate this text.
Content text and files If your site is multilingual, you can configure the content fields on your site to be
translatable. After creating content in one language, you can translate it into other languages. Fields can
contain textual information or uploaded files, and for each field on each content type, you can configure
it to be translatable or non-translatable. You need to have the core Content Translation module installed
in order to translate this text.

Related topics
• Section 10.2, “Adding a Language”
• Section 10.3, “Configuring Content Translation”
• Section 10.4, “Translating Content”

135
CHAPTER 10. 多语言 10.2. ADDING A LANGUAGE

• Section 10.5, “Translating Configuration”

Attributions
Written by Jennifer Hodgdon.

10.2 Adding a Language

Goal
Add one or more languages to your site and define which one is used by default.

Prerequisite knowledge
Section 10.1, “Concept: User Interface, Configuration, and Content translation”

Steps
1. Install the four core multilingual modules (Language, Interface Translation, Content Translation, and
Configuration Translation), by following the steps in Section 4.3, “Installing a Module”.
2. In the Manage administrative menu, navigate to Configuration > Regional and language > Languages
(admin/config/regional/language).
3. Click Add language.
4. Select Spanish (or your preferred language) from the Language name select list. Click Add language.
After waiting for translations to finish downloading, you will be returned to the Languages page, with a
confirmation message and the new language shown.

5. Follow the steps in Section 8.3, “Placing a Block in a Region”to place the Language switcher block in
the Sidebar second region. This will enable site visitors to switch between languages, once the site has
been translated.

136
CHAPTER 10. 多语言 10.3. CONFIGURING CONTENT TRANSLATION

Expand your understanding

• Section 10.3, “Configuring Content Translation”

• Section 10.4, “Translating Content”

Additional resources
Drupal.org page ”Resource Guide: Configuring a Multilingual Site”
Attributions
Written and edited by Leila Tite, Jennifer Hodgdon, and Boris Doesborg.

10.3 Configuring Content Translation

Goal
Make Custom block, Custom menu link, and Content entity types translatable. Select specific subtypes and set
which fields of these can be translated.

Prerequisite knowledge
• Section 2.3, “Concept: Content Entities and Fields”
• Section 10.1, “Concept: User Interface, Configuration, and Content translation”

Site prerequisites
The core Content Translation module must be installed, and your site must have at least two languages. See
Section 10.2, “Adding a Language”.

Steps
1. In the Manage administrative menu, navigate to Configuration > Regional and language > Content lan-
guage and translation (admin/config/regional/content-language).

2. Under Custom language settings, check Content, Custom block and Custom menu link to make these entity
types translatable.

137
CHAPTER 10. 多语言 10.3. CONFIGURING CONTENT TRANSLATION

3. Configuration options appear for Content, Custom block and Custom menu link. Choose the subtypes you
want to translate for each entity type. Check Basic page for Content, Basic block for Custom block and
Custom menu link for Custom menu link.
4. Verify the settings for the entity types as shown below:

Field name Explanation Example value

Default language The default language for the Site’s default language
entity subtype (English)
Show language selector on Whether or not the language Checked
create and edit pages selector should be shown while
editing and creating content

5. Choose the fields that should be translatable for Basic page as shown in the table below. If a field is not
translation-dependent, leave it unchecked. Enabling translation for fields that are numbers or dates has
use for accountability or implementing workflows.

Field name Explanation Example value

Title The title of the content Checked

138
CHAPTER 10. 多语言 10.4. TRANSLATING CONTENT

Field name Explanation Example value

Authored by The author Unchecked
Publishing status Whether the content has been Checked
published or not
Authored on Date of publishing Unchecked
Changed Date of last update Unchecked
Promoted to front page Whether the content will be Unchecked
included in some content views
Sticky at top of lists Whether the content will be Unchecked
displayed first in some content
views
URL alias Nicer URL for the content Checked
Body The main content of the page Checked

6. Similarly, check the appropriate boxes for translatable fields belonging to Basic block and Custom menu
link.
7. Click Save configuration.

Expand your understanding

• Section 10.5, “Translating Configuration”

• Section 10.4, “Translating Content”

Additional resources
• Blog post ”Multilingual Drupal 8 tidbits, part 5”
• Blog post ”Multilingual Drupal 8 tidbits, part 17”

Attributions
Written and edited by Laura Vass at Pronovix, Jojy Alphonso at Red Crackle, and Jennifer Hodgdon.

10.4 Translating Content

Goal
Translate the home page to Spanish.

Prerequisite knowledge
Section 10.1, “Concept: User Interface, Configuration, and Content translation”

Site prerequisites
• The Home content item must exist. See Section 5.2, “Creating a Content Item”.
• The core Content Translation module must be installed, and your site must have at least two languages.
See Section 10.2, “Adding a Language”.
• The Basic page content type must be configured to be translatable. See Section 10.3, “Configuring
Content Translation”.

139
CHAPTER 10. 多语言 10.4. TRANSLATING CONTENT

Steps
1. In the Manage administrative menu, navigate to Content (admin/content).

2. Locate the home page. You can search for it by entering ”Home” in the title field.
3. Select Translate from the dropdown button in the row of the Home content item. The page Translations
of Home appears.
4. Click Add in the row Spanish.

5. Note that the user interface has switched to Spanish. To switch it back to English, remove the first instance
of es in the browser’s URL. For example, if your URL looks like example.com/es/node/5/translations/add/en/es,
remove the es that comes immediately after example.com.
6. Fill in the fields as shown below. You will have to click and expand URL path settings on the right to
provide the value for URL alias.

Field name Explanation Value

Title Translated title of the page Página principal
Body Translated body of the page Bienvenido al mercado de la
ciudad - ¡el mercado de
agricultores de tu barrio!
Horario: Domingos de 9:00 a
14:00. Desde Abril a
Septiembre Lugar: parking del
Banco Trust número 1. En el
centro de la ciudad
URL path settings > URL Translated address of the pagina-principal
alias webpage

7. Click Save and keep published (this translation).

8. Go to your site’s home page to view the newly translated page.

Expand your understanding

• Follow the steps above to translate more content on your site.
• Section 10.5, “Translating Configuration”

Attributions
Written by Boris Doesborg.

140
CHAPTER 10. 多语言 10.5. TRANSLATING CONFIGURATION

10.5 Translating Configuration

Goal
Translate the labels on the Recipes view page into Spanish.

Prerequisite knowledge
• Section 10.1, “Concept: User Interface, Configuration, and Content translation”
• Section 9.3, “Creating a Content List View”

Site prerequisites
• The core Configuration Translation module must be installed, and your site must have at least two
languages. See Section 10.2, “Adding a Language”.
• The Recipes view must exist. See Section 9.3, “Creating a Content List View”and Section 9.4, “Du-
plicating a View”.

Steps
The basic steps for translating any configuration on your site are:
1. Locate the page where the configuration you want to translate is created or edited in the site’s primary
language. For example, to translate the site name, you need to find the page where you would edit the
site name (see Section 4.2, “Editing Basic Site Information”).
2. Find a link, tab, or button on the page that says ”Translate” or something similar. Click this link, tab,
or button.

3. Find a button that will let you add a translation in the desired language, and click this button.
4. Enter the translation in the form, and save.
Most configuration is fairly straightforward and intuitive to edit in this manner. Views configuration is an
exception, because the translation editing form is nothing like the view editing form, and it is complex and
hierarchical rather than being a simple form with just a few fields. As an example of how to translate a view,
here are the steps to translate the labels in the Recipes view to Spanish:
1. In the Manage administrative menu, navigate to Structure > Views (admin/structure/views).
2. Locate the Recipes view and click Translate from the dropdown button.
3. Click Add in the row Spanish. The page Add Spanish translation for Recipes view appears.

4. Find Displays > Master Display settings > Recipes default display Options. Translate the Display title
from ”Recipes” to ”Recetas”.
5. Find Displays > Master display settings > Recipes default display options > Exposed form > Reset options.
Translate Submit button text (Apply) to ”Applicar”. The other buttons and labels in this section do not
appear on the Recipes page or block, and do not need to be translated.

141
CHAPTER 10. 多语言 10.5. TRANSLATING CONFIGURATION

6. Find Displays > Master display settings > Recipes default display options > Filters > (Empty) taxonomy
term ID > Find recipes using…Expose. In the Label field, enter ”Encontrar recetas usando…”.
7. Click Save translation.
8. Navigate to the Recipes page and switch to Spanish using the Language switcher block. Verify that the
labels have been translated.

Expand your understanding

• Translate the block display title in the Recent recipes display settings section of the Recipes view.
• Translate the page title in the Vendors view.
• Translate other configuration. Some examples of where to find the translation pages:

– To translate the site name, navigate in the Manage administrative menu to Configuration > System >
Basic site settings > Translate system information (admin/config/system/site-information/translate).
– To translate the contact form, navigate in the Manage administrative menu to Structure > Contact
forms (admin/structure/contact). Click Translate in the dropdown button in the Website feedback
row.

142
CHAPTER 10. 多语言 10.5. TRANSLATING CONFIGURATION

– To translate the name of a menu, navigate in the Manage administrative menu to Structure > Menus
(admin/structure/menu). Click Translate in the dropdown button for the menu whose name you
want to translate.
– Menu items within a menu are considered to be content (not configuration); see Section 10.3,“Con-
figuring Content Translation”to enable translation. Once translation is enabled, navigate in the
Manage administrative menu to Structure > Menus (admin/structure/menu). Click Edit menu in
the dropdown button for the menu whose links you want to translate. Click Translate in the dropdown
button for the link you want to translate.
– To translate field labels on a content type, navigate in the Manage administrative menu to Structure
> Content types (admin/structure/types). Click Manage fields in the dropdown button for the content
type whose field labels you want to edit. Click Translate in the dropdown button for the field whose
label you want to edit.

• Translate content. See Section 10.4, “Translating Content”.

Attributions
Written and edited by Boris Doesborg and Jennifer Hodgdon.

143
Chapter 11

扩展和自定义网站

11.1 Finding Modules

Goal
Find and evaluate modules on Drupal.org.

Prerequisite knowledge
• Section 1.1, “概念：Drupal 作为一个内容管理系统”
• Section 1.2, “概念：模块”

Steps
1. Go to Drupal.org, and navigate to Download & Extend > Modules (https://www.drupal.org/project/-
project_module).

2. Filter your search using the categories on the module search page. Fill in the fields as shown below.

Field name Explanation Example value

Maintenance status How actively should the Actively maintained
module be maintained?
Development status What kind of development Any
should the module undergo?
Module categories The module’s topic area. Administration
Core compatibility The version of the core 8.x
software the module is
compatible with.
Status Project status: Sandbox Full projects
projects are experimental
projects. Full projects have
already gone through an
approval process, but they can
still be in development.
Search Modules Search for Admin Toolbar, a Admin Toolbar
module that will be covered in
detail later. Alternatively, you
can also leave the field blank if
you are not sure which module
to search for.

145
CHAPTER 11. 扩展和自定义网站 11.1. FINDING MODULES

Field name Explanation Example value

Sort by Order your search results by Most installed
criteria like Most installed
(popular modules that many
sites use) or Last release (date
of latest version released).

3. Click Search. Search results will appear.

146
CHAPTER 11. 扩展和自定义网站 11.1. FINDING MODULES

147
CHAPTER 11. 扩展和自定义网站 11.1. FINDING MODULES

4. To further evaluate a module, click its title in the list of search results to visit its project page.

Some aspects to pay attention to when evaluating modules:

• Project description: The description of the module on its project page should be clear and useful. You
should get an idea of its features and requirements.
• Maintenance status: If a module is Actively maintained, you can be sure that there will be security updates,
bug fixes and feature improvements provided on a regular basis. However, if the module is unmaintained
or abandoned, you shouldn’t use it.
• Development status: Under active development means you can expect new features to be added to the
project, but some aspects (for example, API) may still change. Maintenance fixes only means that the
project is considered feature complete.
• Reported installs, downloads: You can see how many people have downloaded and how many sites use
the module. If it’s only used by a few sites, it might be a unique solution that not many people need, or
it might be a warning sign that you shouldn’t use it either.
• Maintainers: When was the last commit (the last time someone updated something on the module) or
last release (new version)? If the project has few open issues, a long time since commits/releases might
be appropriate, but if it has a lot of open issues and there are no commits/releases, that would be a clue
that it might be abandoned.
• Issues: See if there are any open issues, potential problems with the module. Check the Statistics to see
how regularly issues are responded to.
• Resources: Check if the module has documentation or a README file, that can help you install, configure,
explore, and test it.

Expand your understanding

Section 11.3, “Downloading and Installing a Module from Drupal.org”
Attributions
Written by Diána Lakatos at Pronovix.

148
CHAPTER 11. 扩展和自定义网站 11.2. ENABLING AND DISABLING …

11.2 Enabling and Disabling Maintenance Mode

Goal
Put your site in maintenance mode to allow users with the right permissions to use the site while users without
this permission are presented with a message that the site is under maintenance.

Prerequisite knowledge
Section 13.3, “Concept: Security and Regular Updates”

Steps
Enabling maintenance mode
1. In the Manage administrative menu, navigate to Configuration > Development > Maintenance mode
(admin/config/development/maintenance). The Maintenance mode page appears.
2. Fill in the fields as shown below.

Field name Explanation Value

Put site into maintenance Enable the maintenance mode Checked
mode
Message to display when in The information that is shown @site is currently under
maintenance mode to website visitors when the maintenance but should be
mode is enabled. Variables back shortly. Thank you for
such as @site can be used in your patience.
the message

3. Click Save configuration.

4. Verify that the site is in maintenance mode by accessing it from another browser where you aren’t logged
in. If you are not able to verify, try clearing the cache. See Section 12.2, “Clearing the Cache”.

149
CHAPTER 11. 扩展和自定义网站 11.2. ENABLING AND DISABLING …

Disabling maintenance mode

1. In the Manage administrative menu, navigate to Configuration > Development > Maintenance mode
(admin/config/development/maintenance). The Maintenance mode page appears.
2. Fill in the fields as shown below.

Field name Explanation Value

Put site into maintenance Disable the maintenance mode Unchecked
mode
Message to display when in No message required while
maintenance mode disabling. You can leave the
field blank.

3. Click Save configuration.

150
CHAPTER 11. 扩展和自定义网站 11.2. ENABLING AND DISABLING …

4. Verify that the site is no longer in maintenance mode by accessing it from another browser where you
aren’t logged in. If you are not able to verify, try clearing the cache. See Section 12.2, “Clearing the
Cache”.

Expand your understanding

• Section 13.5, “Updating the Core Software”
• Section 13.7, “Updating a Theme”

• Section 13.6, “Updating a Module”

Attributions
Written and edited by Boris Doesborg, and Jojy Alphonso at Red Crackle.

151
CHAPTER 11. 扩展和自定义网站 11.3. DOWNLOADING AND INSTALLING A …

11.3 Downloading and Installing a Module from Drupal.org

Goal
Download and install the contributed Admin Toolbar module, which allows you to easily browse through the
administration section of the website.

Prerequisite knowledge
• Section 1.2, “概念：模块”
• Section 11.1, “Finding Modules”
• Section 3.2, “Concept: Additional Tools”

Site prerequisites
• If you want to install modules via the website, the core Update Manager module must be installed. See
Section 4.3, “Installing a Module”for instructions on installing modules.

• If you want to use Drush, Drush must be installed. See Section 3.2, “Concept: Additional Tools”.

Steps
You can use the administrative interface or Drush to install a contributed module. If you are installing a
custom module rather than a contributed module, if you see a message saying Installing modules and themes
requires FTP access to your server, or if the steps below do not work to download and unpack the module files,
follow the steps in Section 11.6, “Manually Downloading Module or Theme Files”. If you are installing a
contributed module with external dependencies that are managed by Composer, follow the steps for downloading
in Section 11.9, “Using Composer and Git to Download Files”. In either of these cases, then continue here
with step 7 in the instructions for the administrative interface below.

Using the administrative interface

1. On the Admin toolbar project page on drupal.org (https://www.drupal.org/project/admin_toolbar), scroll
to the Downloads section at the bottom of the page.
2. Copy the address of the tar.gz link. Depending on your device and browser, you might do this by right
clicking and selecting Copy link address.

3. In the Manage administrative menu, navigate to Extend (admin/modules). The Extend page appears.

152
CHAPTER 11. 扩展和自定义网站 11.3. DOWNLOADING AND INSTALLING A …

4. Click Install new module. The Install new module page appears.

5. In the field Install from a URL, paste the copied download link. This value could look like this:
https://ftp.drupal.org/files/projects/admin_toolbar-8.x-1.14.tar.gz
6. Click Install to upload and unpack the new module on the server. The files are being downloaded to the
modules directory.

7. Click Enable newly added modules to return to the Extend page. If you used the manual uploading
procedure, start with this step, and reach the Extend page by using the Manage administrative menu and
navigating to Extend (admin/modules).
8. Locate and check Admin toolbar.

9. Click Install to turn on the new module.

Using Drush
1. Find the project name for the module you want to install, which is the last segment of the module’s
project page URL. For example, if the project URL is https://www.drupal.org/project/admin_toolbar, the
project name is ”admin_toolbar”.

2. Run the following Drush commands, giving the project name (for example, admin_toolbar) as a param-
eter:

153
CHAPTER 11. 扩展和自定义网站 11.4. FINDING THEMES

drush dl admin_toolbar
drush en admin_toolbar

3. Follow the instructions on the screen.

Expand your understanding

• Verify that the contributed Admin Toolbar module is working by browsing through the menu in the
administration section.
• Install and configure the contributed Pathauto module so that content pages in your site get nice URLs
by default. See Section 5.1, “Concept: Paths, Aliases, and URLs”for more on URLs.

• If you do not see the effect of these changes in your site, you might need to clear the cache. See Section 12.2,
“Clearing the Cache”.

Additional resources
• Drupal.org community documentation page ”Contributed modules”
• ”Download and Extend” page on Drupal.org
• Admin Toolbar module on Drupal.org

Attributions
Written and edited by Boris Doesborg and Jennifer Hodgdon.

11.4 Finding Themes

Goal
Find and evaluate themes on Drupal.org.

Prerequisite knowledge
• Section 1.1, “概念：Drupal 作为一个内容管理系统”

• Section 1.3, “概念：主题”

Steps
1. Go to https://www.drupal.org, and navigate to Download & Extend > Themes (https://www.drupal.org/-
project/project_theme).
2. Filter your search using the categories on the theme search page. For example, you might use these filters:

Field name Explanation Example value

Maintenance status How actively is the theme Actively maintained
maintained? If a theme is
actively maintained, you can
expect bug fixes and
improvements on a regular
basis.

154
CHAPTER 11. 扩展和自定义网站 11.4. FINDING THEMES

Field name Explanation Example value

Development status What kind of development is Any
the theme undergoing? If you
select Under active
development, you can expect
new features to be added, and
some aspects may still change.
If you select Maintenance fixes
only, it means that the theme
is considered complete.
Core compatibility The Drupal version the theme 8.x
is compatible with.
Status Sandbox projects are Full projects
experimental projects. Full
projects have already gone
through an approval process,
but they can still be in
development.
Search Themes Search by search term in the -
theme’s description.
Sort by Order your search results by Most installed
criteria like Most installed
(popular themes that many
sites use) or Last release (date
of latest version released).

3. Click Search. Search results will appear.

155
CHAPTER 11. 扩展和自定义网站 11.4. FINDING THEMES

156
 CHAPTER 11. 扩展和自定义网站 11.5. DOWNLOADING AND INSTALLING A …

4. To further evaluate a theme, click its title in the list of search results to visit its project page.

Some aspects to pay attention to while evaluating themes:

• Introduction: The description of the theme on its project page should be clear and useful. A screenshot
of the theme helps your evaluation as well.
• Downloads: The theme should be available for your version of the core software. Pay attention to the
color-coding: Themes marked green are recommended to be used on live sites, the ones marked yellow
should be carefully evaluated before use, and the ones marked red are only recommended for testing.
• Project Information: Check the theme’s maintenance and development status, and how frequently it’s
downloaded and installed.
• Issues: See if there are any open issues or potential problems with the theme.
• Resources: Check if the theme has documentation.

Expand your understanding

• Section 11.5, “Downloading and Installing a Theme from Drupal.org”

Attributions
Written by Diána Lakatos.

11.5 Downloading and Installing a Theme from Drupal.org

Goal
Download and install a theme from Drupal.org.

Prerequisite knowledge
• Section 11.4, “Finding Themes”
• Section 3.2, “Concept: Additional Tools”

Site prerequisites
If you want to install via the website, the core Update Manager module must be installed. See Section 4.3,
“Installing a Module”for instructions on installing modules.
If you want to use Drush, Drush must be installed. See Section 3.2, “Concept: Additional Tools”.

Steps
You can use the administrative interface or Drush to install a contributed theme. If you are installing a custom
theme rather than a contributed theme, if you see a message saying Installing modules and themes requires FTP
access to your server, or if the steps below do not work to download and unpack the theme files, follow the steps
in Section 11.6, “Manually Downloading Module or Theme Files”. If you are installing a contributed theme
with external dependencies that are managed by Composer, follow the steps for downloading in Section 11.9,
“Using Composer and Git to Download Files”. In either of these cases, then continue here with step 7 in the
instructions for the administrative interface below.

157
CHAPTER 11. 扩展和自定义网站 11.5. DOWNLOADING AND INSTALLING A …

Using the administrative interface

1. On the theme’s project page on drupal.org (for example, https://www.drupal.org/project/mayo), scroll
to the Downloads section at the bottom of the page.
2. Right-click tar.gz to copy the address.

3. In the Manage administrative menu, navigate to Appearance (admin/appearance). The Appearance page
appears.

4. Click Install new theme. The Install new theme page appears.

158
CHAPTER 11. 扩展和自定义网站 11.5. DOWNLOADING AND INSTALLING A …

5. In the field Install from a URL, paste the copied download link. This value could look like https://ftp.drupal.org/fil
6. Click Install to upload and unpack the new theme on the server. The files are being downloaded to the
themes directory.
7. Click Install newly added themes to return to the Appearance page. If you used the manual uploading
procedure, start with this step, and reach the Appearance page by using the Manage administrative menu
and navigating to Appearance (admin/appearance).
8. Locate the new theme under Uninstalled themes and click Install and set as default to use it. All non-
administrative pages on the site will now use this new theme.

159
CHAPTER 11. 扩展和自定义网站 11.6. MANUALLY DOWNLOADING MODULE …

Using Drush
1. Find the project name for the theme you want to install, which is the last segment of the theme’s project
page URL. For example, if the project URL is https://www.drupal.org/project/mayo, the project name is
mayo.
2. Run the following Drush commands, giving the project name (for example, mayo) as a parameter:
drush dl mayo
drush en mayo
drush config -set system . theme default mayo

3. Follow the instructions on the screen.

Expand your understanding

• In the Manage administrative menu, navigate to Appearance (admin/appearance) and uninstall any themes
that you are not using.
• Section 11.1, “Finding Modules”
• Section 11.3, “Downloading and Installing a Module from Drupal.org”
• If you do not see the effect of these changes in your site, you might need to clear the cache. See Section 12.2,
“Clearing the Cache”.
Attributions
Written and edited by Joe Shindelar at Drupalize.Me, and Boris Doesborgh.

11.6 Manually Downloading Module or Theme Files

Goal
Manually download module or theme files and upload them to your site, if the website or Drush methods for
installing or updating a module or theme do not work, or if you are placing a custom-written module or theme.

160
CHAPTER 11. 扩展和自定义网站 11.6. MANUALLY DOWNLOADING MODULE …

Prerequisite knowledge
• Section 1.2, “概念：模块”

• Section 11.1, “Finding Modules”

• Section 1.3, “概念：主题”
• Section 11.4, “Finding Themes”

Site prerequisites
You need to be facing any of the following to perform the manual download described in this topic:
• File permission issues

• FTP permission issues

• You created a custom module/theme or received its files from someone
• You could not successfully complete the instructions in Section 11.3,“Downloading and Installing a Mod-
ule from Drupal.org”, Section 11.5,“Downloading and Installing a Theme from Drupal.org”, Section 13.6,
“Updating a Module”, or Section 13.7, “Updating a Theme”
Skip this topic if none of the above applies to you.

Steps
If you are installing a module or theme from Drupal.org, follow the downloading instructions, and then the up-
loading/unpacking instructions. If you created the module or theme, skip the downloading step. Instead, create
an archive file (that you know how to extract on the server) and proceed with the steps in uploading/unpacking,
using whatever method is appropriate for the way you initially created the archive file.

Downloading the files

1. Open the module or theme project page on drupal.org; for example, the Admin toolbar page (https://www.drupal.org/-
project/admin_toolbar).
2. Scroll to the Downloads section near the bottom of the page.

3. Click tar.gz to download the file to your computer.

Uploading the files to your site and unpacking them

1. If you are adding a new module or theme, create subdirectories in your top-level modules and themes
directories (if they don’t already exist). Typically, people make a contrib subdirectory for contributed
modules and themes that are downloaded from Drupal.org, and a custom subdirectory for modules and
themes that they created. Your modules directory might look like this:

161
CHAPTER 11. 扩展和自定义网站 11.6. MANUALLY DOWNLOADING MODULE …

2. If you are replacing an existing module or theme with an updated version, put the site into maintenance
mode. See Section 11.2, “Enabling and Disabling Maintenance Mode”.
3. If you are replacing an existing module or theme with an updated version, find and delete all the existing
files and directories for the existing module or theme. Modules are normally located in directories under
the top-level modules directory, and themes are normally located in directories under the top-level themes
directory.
4. Upload the .tar.gz file (or whatever archive you created) to your site. Place it in either the same loca-
tion from which you deleted the directory (if replacing an existing module or theme) or the appropriate
subdirectory of modules or themes (if adding a new module or theme).
5. Extract the files from the .tar.gz archive (or whatever archive you created), making a subdirectory in
the same location as the archive file. If you do not have terminal access, or your hosting server is not
running Linux, your hosting control panel’s file manager should provide a way to extract the files. If you
have terminal access to your hosting server (running Linux) and you are using a tar.gz file, you can use a
command like:
tar -xzf admin_toolbar -8.x -1.17. tar.gz

6. Delete the compressed file from the server, unless your unpacking method already deleted it.
7. Refer to Section 11.3, “Downloading and Installing a Module from Drupal.org”, Section 11.5, “Down-
loading and Installing a Theme from Drupal.org”, Section 13.6, “Updating a Module”, or Section 13.7,
“Updating a Theme”to complete the installation or update of the module or theme. Start at the step
after the automatic download has been completed.

Expand your understanding

• If you work with multiple environments (for example, a local development site and a production site)
you will have to repeat the steps on each environment, or re-clone the environment. See Section 11.8,
“Making a Development Site”.
• If you added a new theme, navigate in the Manage administrative menu to Appearance (admin/appearance)
and uninstall the old theme.

Additional resources
• Drupal.org community documentation page ”Updating modules”
• Drupal.org community documentation page ”Installing contributed modules (Drupal 8)”

• Drupal.org community documentation page ”Installing themes”

Attributions
Written and edited by Boris Doesborg, Jennifer Hodgdon, and Marc Isaacson.

162
CHAPTER 11. 扩展和自定义网站 11.7. CONCEPT: DEVELOPMENT SITES

11.7 Concept: Development Sites

What are Development Sites?
Development Sites are different copies of the same site used for developing, updating, and testing a site without
risking the integrity of the live site.
An example deployment workflow for site building will usually include the sites mentioned below:

Local environment The development process starts with developers working on new features, bug fixes,
theming, and configuration in their local environment.
Development site Developers push the changes they’ve been working on to the development site. For a
team of more than one developer, version control is usually used. Git is a version control system that
tracks your files for any changes. You can then commit those changes to a repository. Using Git allows
team members to work on the same site without overriding each other’s work. It also makes it possible
to easily roll back to previous stages of the development.
Staging site The staging site can be used for testing, or presenting the changes to the client for approval.
QA (Quality Assurance) and UAT (User Acceptance Testing) are most often carried out on the staging
site. It is recommended to have live content on both the development and staging sites, so that you can
test how the new features will work with the existing content.
Production site The live site on the web available to visitors. It contains new features that have been
proven safe to go live.
Based on the project’s size, scope, requirements, or stakeholders, stages from the above workflow can be
removed, or additional stages can be added. For example, a testing site before staging can be added to separate
testing and user acceptance processes.

Related topics
• Section 11.8, “Making a Development Site”

• Section 2.6, “Concept: Editorial Workflow”

Additional resources
Drupal.org community documentation page ”Introduction to Git”
Attributions
Written and edited by Diána Lakatos, and Jojy Alphonso at Red Crackle.

11.8 Making a Development Site

Goal
Make a copy of a site that you can use to develop new features and test updates on.

Prerequisite knowledge
Section 11.7, “Concept: Development Sites”

Site prerequisites
• You have a live, developed site that you would like to make a copy of for development purposes.
• If you want to use Drush for some of the steps in this task, Drush must be installed. See Section 3.2,
“Concept: Additional Tools”.

163
CHAPTER 11. 扩展和自定义网站 11.8. MAKING A DEVELOPMENT SITE

Steps
1. Follow the steps in Section 3.3,“Preparing to Install”, so that you have hosting set up for your development
site, you know where the web root is for your development site, and you have an empty database and
database user for your development site to use.
2. Make a database dump file from your live site’s database. Try one of the following methods:

• If you are using MySQL as your database, and your live site’s server has phpMyAdmin installed
(it is available from many hosting control panels), use the Export tab in phpMyAdmin to export in
SQL format. Using gzip compression on the output file is suggested, to reduce the file size.
• If you are using MySQL and have access to the command line, use this command (substituting in
your site’s database name, user name, and password):
mysqldump -u USERNAME -p'PASSWORD ' DATABASENAME > BACKUPFILE .sql

• If you prefer to use Drush, use this command:

drush sql -dump > BACKUPFILE .sql

• Use the contributed Backup and Migrate module from within your live site. See Section 11.3,
“Downloading and Installing a Module from Drupal.org”for instructions on installing contributed
modules.
You now have a database dump stored in the file BACKUPFILE.sql. For security reasons, avoid
storing this file on your hosting server anywhere under the Drupal site root. This will prevent others
from getting a copy of your database.

3. Copy all of the files from the web root of your live site to the web root of your development site.
4. Edit the sites/default/settings.php file under your development site’s top-level directory in a plain-text
editor. Find the lines near the end that contain the database name, database username, and database
password, and update them to the information about the development site database you set up. The lines
look something like this (before editing):
$databases ['default '][' default '] = array (
'database ' => 'live_site_database_name ',
'username ' => 'live_site_database_username ',
'password ' => 'live_site_database_password ',

5. Check whether your settings.php file has the following setting; if yes, then you will need to edit this to
point to your development site URL instead of your production site URL:
$settings [' trusted_host_patterns ']

6. Import the database dump file you created, into the development site’s database. Try one of the following
methods:

• If you are using MySQL as your database, and your live site’s server has PHPMyAdmin installed
(it is available from many hosting control panels), use the Import tab in PHPMyAdmin. You may
find that you have to restart the import a few times, if your database was large.
• If you are using MySQL and have access to the command line, use this command (substituting in
your site’s database name, user name, and password; if you made a gzip-compressed backup file,
you will also need to uncompress it first):
mysql -u USERNAME -pPASSWORD DATABASE_NAME < BACKUPFILE .sql

• If you prefer to use Drush, use this command:

drush sql - query --file= BACKUPFILE .sql

164
CHAPTER 11. 扩展和自定义网站 11.9. USING COMPOSER AND GIT TO …

7. If your development and live sites need to have different configuration, then you have to use configuration
overrides in the settings.php file. The $config variable will help you maintain override values separately
from the standard configuration data. For instance, you might want the site name to be ”Anytown Farmers
Market” on the production site, but ”Development Site for Anytown Farmers Market” on the development
site. To do that, you could have the production value in the site configuration (in the database), and on
the development site, in the settings.php file, you would need to have:
$config [' system .site '][' name '] = " Development Site for Anytown Farmers Market ";

Expand your understanding

• Verify that the development site is working correctly.
• Log in to the development site as an administrator, and clear the cache. See Section 12.2, “Clearing the
Cache”.
• Section 11.10, “Deploying New Site Features”

Additional resources
• Drupal.org community documentation page ”Backing up a site”
• Drupal.org community documentation page ”Create a Test Site”
Attributions
Written and edited by Jennifer Hodgdon, Joe Shindelar at Drupalize.Me, and Jojy Alphonso at Red Crackle.

11.9 Using Composer and Git to Download Files

Goal
Use Composer and/or Git to download files and dependencies in the core software, or in add-on modules and
themes.

Prerequisite knowledge
• Section 3.2, “Concept: Additional Tools”
• Section 11.7, “Concept: Development Sites”

Site prerequisites
If you want to use Git or Composer, they must be installed either on a local development server or your live
site. See Section 3.2, “Concept: Additional Tools”.

Steps
If you are unable to install the Git or Composer tools on your live server, after following the steps in any of the
sections below on your local server, you will need to transfer any updated or added files to your live server. The
recommended procedure is to make an archive or zip file of the new and changed files, transfer the archive to
your live server, and extract it there. If you are using Composer, make sure to check for updates and additions
to the following files, in the root of your installation:
• vendor directory
• autoload.php
• composer.json
• composer.lock

165
CHAPTER 11. 扩展和自定义网站 11.9. USING COMPOSER AND GIT TO …

Using Git to download a project

Follow these steps if you want to download the development version of the core software, or of a contributed
module or theme, from the project’s Git version control repository:
1. In a command-line window, change to one level above the directory where you want the files to reside.
For the core software, this would be your web root. For an add-on module, this would be the modules
directory, or a sub-directory like contrib under the modules directory.
2. Locate the page for the project that you want to download on Drupal.org; for example, https://www.drupal.org/-
project/drupal for the core software, or https://www.drupal.org/project/admin_toolbar for the con-
tributed Admin Toolbar module.
3. Click the Version control link near the top of the page, which opens up a page giving Git commands for
this project.
4. Copy the git clone command under Setting up repository for the first time, and paste it into your
command line. For example, it might be:
git clone --branch 8.2.x https :// git. drupal .org/ project / drupal .git

5. This will create a directory named with the short name of the project (drupal in this example), and
download the required files into that directory. If necessary, rename the directory.
6. If you downloaded the drupal project (the core software), follow the instructions below to download its
external dependencies.
7. Later on, you can change to the created directory and run the command git pull to update the files to
the latest version from the Git repository for the project.

Using Composer to download external core dependencies

Follow these steps if you downloaded the core software files using Git, which does not include the external
dependencies:
1. Change to the core software’s root directory.
2. Run the command composer install at the command line. The external dependencies will be down-
loaded.

Using Composer to download the core software

Follow these steps if you have not yet downloaded or installed the core software, and you want to use Composer
to download both the core software and its external dependencies:
1. At the command line, change to one level above the directory where you want the software to reside.
2. Enter this command, where my_site_name is the directory you want to create:
composer create - project drupal / drupal my_site_name

Using Composer to download a module or theme

Follow these steps if you have already downloaded the core software, and you want to use Composer to add a
contributed module or theme (usually because it has external dependencies that need to be downloaded with
Composer):
1. If you have not already done so, tell Composer about the download location for contributed modules and
themes, by entering this command from the root of your site installation:
composer config repositories . drupal composer https :// packages . drupal .org /8

166
CHAPTER 11. 扩展和自定义网站 11.10. DEPLOYING NEW SITE FEATURES

2. If you have not already done so, you can optionally override the default location where Composer will put
downloaded modules and themes. For example, typically you would want contributed modules to go in
a contrib subdirectory of the top-level modules directory, instead of the default location of modules. To
make this change, edit the composer.json file at the root level in your site installation. Find the line that
says "extra": {, and add these lines following that line:
"installer -paths ": {
" modules / contrib /{ $name }": [" type:drupal - module "],
" modules / custom /{ $name }": [" type:drupal -custom - module "],
" profiles / contrib /{ $name }": [" type:drupal - profile "],
" themes / contrib /{ $name }": [" type:drupal - theme "],
" themes / custom /{ $name }": [" type:drupal -custom - theme "],
" libraries /{ $name }": [" type:drupal - library "],
"drush /{ $name }": [" type:drupal -drush "]
},

3. Each time you want to add a contributed module or theme, determine the project’s short name. This is the
last part of the URL of the project page; for example, the Geofield module, at https://www.drupal.org/-
project/geofield, has short name geofield.
4. To download the contributed module or theme, along with its external dependencies, enter the following
command at the root of your site (substituting the short name of the module or theme for geofield):
composer require drupal / geofield

Using Composer to update a project’s files

Follow these steps to update the files for the core software or a contributed module or theme, after having
already started to manage dependencies with Composer:
1. Determine the short name of the project you want to update. For the core software, it is drupal. For
contributed modules and themes, it is the last part of the URL of the project page; for example, the
Geofield module, at https://www.drupal.org/project/geofield, has short name geofield.
2. Determine how to enter the version number you want to update to. For example, for version 8.x-1.7 of a
contributed module, you would enter just the 1.7, and for the core software version 8.3.1, you would enter
3.1.

3. Enter the following command at the root of your site (substituting the short name of the module or theme
for geofield and the correct version number):
composer require drupal / geofield :1.7

Additional resources
Drupal.org community documentation page ”Using Composer with Drupal”
Attributions
Adapted by Jennifer Hodgdon from ”Using Composer with Drupal”, copyright 2000-2017 by the individual
contributors to the Drupal Community Documentation.

11.10 Deploying New Site Features

Goal
Copy a view that you have created in a local development site to the production site.

167
CHAPTER 11. 扩展和自定义网站 11.10. DEPLOYING NEW SITE FEATURES

Prerequisite knowledge
• Section 11.8, “Making a Development Site”

• Section 11.11, “Synchronizing Configuration Versions”

• Section 11.7, “Concept: Development Sites”

Site prerequisites
• The core Configuration Manager module must be installed in both the development and production sites.
See Section 4.3, “Installing a Module”for instructions on installing core modules.
• The Vendor content type must exist in both the development and production sites, with the same fields.
See Section 6.1, “Adding a Content Type”.

• The Vendors view must exist in the development site but not the production site. See Section 9.3,
“Creating a Content List View”.

Steps
1. Open the local development site.
2. In the Manage administrative menu, navigate to Configuration > Development > Configuration synchro-
nization > Export > Single item (admin/config/development/configuration/single/export). The Single
export page appears.

3. Select View from the Configuration type list.

4. Select Vendors from the Configuration name list. The configuration appears in the textarea.
5. Copy the configuration from the textarea.

168
CHAPTER 11. 扩展和自定义网站 11.10. DEPLOYING NEW SITE FEATURES

6. Open the production site.

7. In the Manage administrative menu, navigate to Configuration > Development > Configuration synchro-
nization Import > Single item (admin/config/development/configuration). The Import page appears.
8. Select View from the Configuration type list.

9. Paste the configuration in the textarea.

10. Click Import. The confirmation page appears.
11. Click Confirm.
12. Verify that the view was imported by navigating in the Manage administrative menu to Structure > Views.

169
CHAPTER 11. 扩展和自定义网站 11.11. SYNCHRONIZING CONFIGURATION …

Expand your understanding

The steps in this topic show how to export and import a single configuration item. However, often if you develop
functionality on a development website and want to transfer it to your production site, you will need to transfer
multiple configuration items. For instance, if you developed a new content type with fields, you would need to
transfer several configuration items for each field, one for the content type itself, and possibly multiple view
mode and form mode items, and they would have to be transferred in the right order. Getting this right can
be both tedious and difficult.
As an alternative, you can export and import the complete configuration of the site. For this, you would need
a local development site that is a clone of the production site (see Section 11.8, “Making a Development Site”
), and then you can follow the steps in Section 11.11, “Synchronizing Configuration Versions”to synchronize
configuration between development and production sites.
Another alternative is to use the contributed Features module, which allows exporting and importing bundled
functionality (for example, all the configuration for a photo gallery).
Finally, if you do not see the effect of these changes in your site, you might need to clear the cache. See
Section 12.2, “Clearing the Cache”.

Related concepts
• Section 11.7, “Concept: Development Sites”

• Section 2.6, “Concept: Editorial Workflow”

Attributions
Written by Boris Doesborg.

11.11 Synchronizing Configuration Versions

Goal
Synchronize the configuration between a development and live site.

Prerequisite knowledge
• Section 1.5, “Concept: Types of Data”
• Section 3.3, “Preparing to Install”
• Section 11.7, “Concept: Development Sites”
• Section 11.8, “Making a Development Site”

Site prerequisites
• You must have a development copy of your production site. See Section 11.8, “Making a Development
Site”.

• The core Configuration Manager module must be installed on both the development and production sites.
See Section 4.3, “Installing a Module”for instructions on how to install core modules.
• You must have changed configuration on either the production or development site (the source site), and
want to synchronize the changes to the other site (the destination site). As an example, you can develop a
new content type, fields, and views on your development site, and when it is all working correctly, deploy
the changes to the live site.
• All configuration that should not be synchronized between the source and destination sites must be stored
in configuration overrides in the settings.php file rather than in the database. See Section 11.8, “Making
a Development Site”.

170
CHAPTER 11. 扩展和自定义网站 11.11. SYNCHRONIZING CONFIGURATION …

Steps
1. In the source site, in the Manage administrative menu, navigate to Configuration > Development >
Configuration synchronization > Export (admin/config/development/configuration/full/export).
2. Click Export. Your site will generate an archive of the full site configuration. Save the file on your local
computer.
3. In the destination site, in the Manage administrative menu, navigate to Configuration > Development >
Configuration synchronization > Import (admin/config/development/configuration/full/import).

4. Browse to find the downloaded configuration archive, and click Upload. Your configuration archive will
be uploaded to the destination site, and you will be redirected to the configuration Synchronize page
(admin/config/development/configuration) with a message saying your files were uploaded.
5. Verify that the differences shown on the page are what you expect. You may see configuration items that
have been added, deleted, or changed; for changed items, you can click View differences to see what the
changes are.
6. When you are satisfied, click Import all to import the configuration changes.

Expand your understanding

• If the changes you have made involve only one configuration item (such as one view), you can use the single
configuration export/import feature to deploy the change between sites. See Section 11.10, “Deploying
New Site Features”.
• After the step where you export the full configuration from the source site, you might also want to
unpack the archive and commit it to a version control system, such as Git, to track changes in your site
configuration. See Section 3.2, “Concept: Additional Tools”.

Attributions
Written by Jennifer Hodgdon.

171
Chapter 12

防止和修复问题

12.1 Concept: Cache

Prerequisite knowledge
Section 1.1, “概念：Drupal 作为一个内容管理系统”

What is the page cache?

The software that runs your site, on each page request, must perform calculations and retrieve data from the
database, in order to compose the page that is sent to the web browser or other application that is accessing the
site. These calculations take time, which can mean that your page load time is longer than would be desirable.
There are several ways that page load time can be sped up, including installing software on the server. The
system includes the core Internal Page Cache and Dynamic Page Cache modules, which do not require any
additional server software; they use a database cache mechanism to speed up your site. The way these modules
work is that during page calculations, intermediate results and the final page output are stored in a special
database area (known as the cache). Then the next time a compatible request is made, intermediate or final
results, as appropriate, can be retrieved and used rather than redoing the entire calculation. In addition, when
content or data that affects a particular calculation is updated, the affected cached data is removed from the
cache, forcing that part of the calculation to be redone the next time it is needed.
These caching modules normally work reasonably well, and offer at least some speed-up for most sites.
However, sometimes the page cache can have problems, such as:
• Corrupted data in the cache, leading to garbled or incorrect page output

• Old data remaining in the cache too long, leading to outdated page output
• Insufficient caching, leading to slow page loads

What other data is cached?

Independent of whether the two page cache modules are installed on your site, the software that your site runs
will still cache the output of many internal calculations. The core systems that cache data include:
• The theme system caches information in the database cache about which template files are used to render
various types of data. If you are developing a new theme and add a new template file, you’ll need to
clear this cache to have your theme file recognized.
• CSS and JavaScript files can optionally be optimized and compressed (depending on your site settings).
If so, the compressed versions are stored in the file system so that they don’t have to be re-optimized
too often. If you are developing a module or theme, you may need to either turn off or clear this file cache
to have changes to CSS or JavaScript files be recognized.

173
 CHAPTER 12. 防止和修复问题 12.2. CLEARING THE CACHE

• The system locates certain low-level PHP functions and classes, such as hook implementations and plugin
classes, from your installed modules and stores information about which module has which functionality.
If you are developing a new module or adding features to an existing module, you may need to clear this
cache to have your new features be recognized.

Related topics
If you have problems with your site, the first thing to try to fix it is usually to clear the cache. See Section 12.2,
“Clearing the Cache”for more information.

Additional resources
Learn about additional caching and performance optimization methods in the Drupal.org community documen-
tation page ”Caching to improve performance”.
Attributions
Written by Jennifer Hodgdon.

12.2 Clearing the Cache

Goal
Clear or rebuild your site’s internal caches to ensure they are up-to-date with the most recent data, using the
user interface or Drush.

Prerequisite knowledge
• Section 12.1, “Concept: Cache”

• Section 3.2, “Concept: Additional Tools”

Site prerequisites
If you want to use Drush to clear the cache, Drush must be installed. See Section 3.2, “Concept: Additional
Tools”.

Steps
You can use the administrative interface or Drush to clear the cache.

Using the administrative interface

1. In the Manage administrative menu, navigate to Configuration > Development > Performance (admin/-
config/development/performance).
2. Click Clear all caches.

3. A message saying the cache has been cleared appears at the top of the page.

Using Drush
You can use one of two commands:
• Use the command drush cache-rebuild to clear and rebuild all cached data for a site. After running
this command, you will see the output message ”Cache rebuild complete.”

• Use the command drush cc to see a list of individual caches and then choose the specific cache you would
like to clear. Running this command should produce output like the following:

174
CHAPTER 12. 防止和修复问题 12.3. CONCEPT: DATA BACKUPS

> drush cc
Enter a number to choose which cache to clear.
[0] : Cancel
[1] : drush
[2] : theme - registry
[3] : menu
[4] : css -js
[5] : block
[6] : module -list
[7] : theme -list
[8] : render
[9] : views

Choose a cache to clear by entering the number associated with that cache. Press ”Enter” to continue.

Additional resources
Drupal.org community documentation page ”Clearing or rebuilding Drupal’s cache”
Attributions
Adapted and edited by Joe Shindelar and Jack Haas from ”Clearing or rebuilding Drupal’s cache”, copyright
2000-2017 by the individual contributors to the Drupal Community Documentation.

12.3 Concept: Data Backups

Prerequisite knowledge
• Section 1.1, “概念：Drupal 作为一个内容管理系统”
• Section 3.3, “Preparing to Install”

What is a site backup?

If something happens to the computer (or computers) that your site and its database are running on, or if you
lose access to this computer, you could lose some or all of your site’s data. You could also lose data if your site
is hacked, or if someone with administrative privileges on your site deletes or alters data mistakenly from the
administrative interface. In order to prevent scenarios like this from being permanent, expensive data losses, it
is important to make regular backups of your site’s data, and to store them in a location that is separate from
the computer where your site is running.
The frequency with which you should make data backups, and how many backups you should keep, depends
on how frequently your site is changing. If you have a very large amount of content on your site that is being
added to or updated many times per day, you would want to make more frequent backups than you would for
a site that changes rarely. Also consider that some time could pass between when a data problem occurs and
when you notice that it is a problem, so storing a sequence of backups (so that you can go back to the last
known good data and retrieve that), rather than overwriting a single backup repeatedly, is a good practice.
Another consideration is that whatever format you store your backups in, it is a good idea to verify that you
can actually retrieve lost data from your backups. You might want to test several possible data loss scenarios,
and make sure that your data can be restored to the site in all cases.
In order to make a complete backup of your site, you will need to make copies of the following:
• The data in the sites directory, including the sites/default/settings.php file.
• The data in your site’s database. A few tables can be truncated, such as those storing the temporary
data cache and user login session information, but it is always safe to back up the entire database.
• Uploaded files, such as images and other attachments. The location of these files is configurable; the
standard location is the sites/default/files directory under your site root. In the Manage administrative
menu, navigate to Configuration > Media > File system (admin/config/media/file-system) to check the
file upload locations; to change them, you’ll need to edit your settings.php file.

175
CHAPTER 12. 防止和修复问题 12.4. CONCEPT: LOG

• Modules, themes and any other software files you have customized. You can find customized modules and
themes in the modules and themes directories respectively. Some people prefer to back up all software
files, including core files and contributed modules and themes (which you could recover by downloading
them again from the source), rather than trying to pick out specific files that definitely need to be backed
up.
You can perform a test to confirm whether your backup has been done right by making a development copy
of the site (see Section 11.8, “Making a Development Site”).

Related topics
• Section 13.5, “Updating the Core Software”

• Section 11.8, “Making a Development Site”

• Section 12.1, “Concept: Cache”

Additional resources
• Drupal.org community documentation page ”Backing up a site”
• The contributed Backup and Migrate module, which can be used to set up automatic backups of the
database and uploaded files.

Attributions
Written by Jennifer Hodgdon.

12.4 Concept: Log

What is a Log?
Your site captures system events in a log to be reviewed by an authorized individual at a later time. The log is a
list of recorded events containing usage data, performance data, errors, warnings, and operational information.
It is vital to check the log on a regular basis as it is often the only way to tell what is going on.
You can find your site’s recent log messages in the Manage administrative menu by navigating to Reports
> Recent log messages (admin/reports/dblog).

176
CHAPTER 12. 防止和修复问题 12.5. CONCEPT: STATUS REPORT

Attributions
Adapted by Diána Lakatos from ”Reports” copyright 2000-2017 by the individual contributors to the Drupal
Community Documentation

12.5 Concept: Status Report

What is a Status Report?
The status report is a short overview of your site’s parameters as well as any problems detected with your
installation. It may be useful to copy and paste this information into support requests filed on Drupal.org’s
support forums and project issue queues or when asking for help on other channels.
You can find the status report in the Manage administrative menu by navigating to Reports > Status report
(admin/reports/status).

177
CHAPTER 12. 防止和修复问题 12.5. CONCEPT: STATUS REPORT

Related topics
Section 14.2, “Getting Support”
Attributions
Adapted by Diána Lakatos from ”Reports” copyright 2000-2017 by the individual contributors to the Drupal
Community Documentation

178
Chapter 13

安全和维护

13.1 Concept: Cron

What are cron tasks?
To ensure that your site and its modules continue to function well, a group of administrative operations should
be run periodically. These operations are called cron tasks. Examples of cron tasks are: checking for module
and theme updates, indexing content for search, or cleaning up temporary files.

What is the relationship between the site’s cron tasks and Unix cron?
Linux/Unix-based operating systems have a cron scheduler that can be used to run periodic tasks. You can
use the server’s cron scheduler to schedule runs of the site’s cron tasks. Alternatively, you can use the core
Automated Cron module to run tasks. You can check the site’s cron tasks’ status in the status report.

Related topics
• Section 13.2, “Configuring Cron Maintenance Tasks”
• Section 12.5, “Concept: Status Report”

Additional resources
Drupal.org community documentation page ”Setting up cron”
Attributions
Written and edited by Diána Lakatos at Pronovix, Dave Hansen-Lange at Advomatic, and Boris Doesborg.

13.2 Configuring Cron Maintenance Tasks

Goal
Check whether cron maintenance tasks are run regularly, and if not, either install the core Automated Cron
module or run cron maintenance tasks from outside the website.

Prerequisite knowledge
Section 13.1, “Concept: Cron”

179
CHAPTER 13. 安全和维护 13.2. CONFIGURING CRON MAINTENANCE …

Steps
1. Review the Status report (see Section 12.5, “Concept: Status Report”) to see when cron maintenance
tasks were last run.
If you installed the website using the core Standard installation profile (or similar), then cron maintenance
tasks might already be running via the core Automated Cron module. By default, these tasks are run
about every three hours.
2. Choose whether to run cron maintenance tasks using the core Automated Cron module, or by other means.
The core Automated Cron module might not be suitable for some websites because:

• Each time someone accesses a page on the site, the module checks how long it has been since cron
maintenance tasks have last run, and then runs them if necessary. If no one visits the website for a
long time, cron maintenance tasks will not be run.
• Cron maintenance tasks are run after the page has been generated. This means there is less time for
the tasks to be run before various server timeouts are reached (for example, PHP execution timeout).
If this happens, the logs (see Section 12.4, “Concept: Log”) will show error messages that cron is
unable to complete.
• There is a small scalability cost associated with the core Automated Cron module. This is because
one of the web server’s processes is occupied (and can’t serve other web pages) until the cron
maintenance tasks are complete.

3. If you want to use the core Automated Cron module, first make sure it is installed (it is installed with the
core Standard install profile; see Section 4.3, “Installing a Module”if it is not installed).
Next, configure the module to control how frequently cron maintenance tasks are run. In the Manage
administrative menu, navigate to Configuration > System > Cron (admin/config/system/cron). Choose
the desired interval in the Cron settings section, and click Save configuration.

4. If you want to run cron maintenance tasks from outside the website, uninstall the core Automated Cron
module (see Section 4.4,“Uninstalling Unused Modules”). Next, find the cron URL. This URL is shown in
the Status report (see Section 12.5,“Concept: Status Report”), and in the Cron administration page (see
previous step). The URL looks like this: http://www.example.com/cron/0MgWtfB33FYbbQ5UAC3L0LL3RC0PT3RNU

180
CHAPTER 13. 安全和维护 13.3. CONCEPT: SECURITY AND REGULAR …

Whenever this URL is visited, cron maintenance tasks will run. Set up one of the following schedulers to
access this URL regularly:

• The Cron daemon (Linux, OS X, Solaris, BSD)

• Scheduled Tasks (Windows)
• A cron SASS provider (software as a service)
• A cron manager provided by your web hosting provider (see the documentation provided by your
provider)

Related concepts
Section 13.3, “Concept: Security and Regular Updates”

Additional resources
• Drush page ”Running Drupal cron tasks from Drush”

• Drupal.org community documentation page ”Setting up cron”

Attributions
Written and edited by Dave Hansen-Lange at Advomatic, Boris Doesborg, and Jennifer Hodgdon.

13.3 Concept: Security and Regular Updates

Prerequisite knowledge
• Section 1.1, “概念：Drupal 作为一个内容管理系统”
• Section 1.2, “概念：模块”
• Section 1.3, “概念：主题”
• Section 1.6, “概念：Drupal 项目”

What are security updates?

Any software occasionally has bugs, and sometimes these bugs have security implications. When security bugs
are fixed in the core software, modules, or themes that your site uses, they are released in a security update.
You will need to apply security updates in order to keep your site secure. See Section 13.4, “Keeping Track
of Updates”to learn how to be notified of security updates by email, and Section 13.5, “Updating the Core
Software”, Section 13.6, “Updating a Module”, and Section 13.7, “Updating a Theme”to learn how to
make updates.

What is the security team?

The Drupal open-source project has a team of volunteers who track security-related bugs and release security
updates. They also help other developers fix bugs, and maintain information for users on how to keep their
websites secure. You can learn more about the security team and their practices and processes at the Drupal.org
Security Team page.

How are security bugs reported?

It is important that security problems be kept confidential until they are fixed, so that sites are less likely to
be compromised before they can be secured. If you find a potential security problem in any of the software you
downloaded from the Drupal.org website, follow the procedures on the Drupal.org Security Team page to report
it.

181
CHAPTER 13. 安全和维护 13.4. KEEPING TRACK OF UPDATES

What are regular (non-security) updates?

The core software, modules, and themes also periodically have regular updates to add new features and fix bugs.
These updates are less critical than security updates. As a general best practice, updates should be applied as
long as they do not cause problems with your site. Testing on a development copy of your site is always a good
idea before applying updates on a live site. This is because some updates may include changes that are not
compatible with the modules or themes on your site, or that will break a particular functionality on your site.

Related topics
• Section 13.4, “Keeping Track of Updates”
• Section 13.5, “Updating the Core Software”
• Section 13.6, “Updating a Module”

• Section 13.7, “Updating a Theme”

• Section 11.8, “Making a Development Site”

Additional resources
• Drupal.org community documentation page ”Securing your site”
• ”Security advisories” on Drupal.org
• Drupal.org Security team

Attributions
Written and edited by Boris Doesborg and Jennifer Hodgdon.

13.4 Keeping Track of Updates

Goal
Keep your site safe and up-to-date by keeping up with the latest security updates.

Prerequisite knowledge
Section 13.3, “Concept: Security and Regular Updates”

Steps
There are a few different ways to receive notifications of security releases:
• In the Manage administrative menu, navigate to Reports > Available updates > Settings. Enter the email
addresses to be notified when updates are available. You can also specify whether you want daily or
weekly updates. Click Save configuration.
• Subscribe to the security announcements email list. To subscribe, log in to Drupal.org, go to your user
profile page and subscribe to the security newsletter on the Edit > My newsletters tab.

• Follow @drupalsecurity on Twitter.

• Subscribe to RSS feeds for core security updates, contributed project updates and public service announce-
ments.

182
CHAPTER 13. 安全和维护 13.5. UPDATING THE CORE SOFTWARE

Related concepts
• Section 13.3, “Concept: Security and Regular Updates”

• Section 13.5, “Updating the Core Software”

• Section 13.6, “Updating a Module”
• Section 13.7, “Updating a Theme”

Additional resources
• ”Security advisories” on Drupal.org
• Drupal.org Security Team

• @drupalsecurity on Twitter

Attributions
Written by Sarah German at Advomatic.

13.5 Updating the Core Software

Goal
Update the core software, either through the administrative interface or by using Drush.

Site prerequisites
• If you want to use Drush, Drush must be installed. See Section 3.2, “Concept: Additional Tools”.
• If your site is live, you should test this process in a development environment before running it on your
production site. See Section 11.8, “Making a Development Site”.

Steps
1. Make a complete backup of your site. Refer to Section 12.3, “Concept: Data Backups”.
2. Open settings.php (/sites/default/settings.php) in any plain text editor. Find the line with the $set-
tings[update_free_access] variable. By default, it is set to ”FALSE” due to security reasons. Change the
setting to ”TRUE”:
$settings [' update_free_access '] = TRUE;

3. Disable any caching technique (memcache, varnish, and so on) your application might be using.
4. Put your site in maintenance mode. See Section 11.2, “Enabling and Disabling Maintenance Mode”.
5. If you are using Composer to manage dependencies, or using Git, skip the next six steps, and instead see
Section 11.9, “Using Composer and Git to Download Files”for instructions on downloading updated
files. Continue with the update.php step.
6. Download the tar.gz or zip file archive for the latest version of Drupal 8.x core from Drupal.org Drupal
Core Downloads. See Section 3.3,“Preparing to Install”for more details on how to find the latest version.
7. Upload the archive file to your web hosting server.

8. Extract the archive file to a temporary directory on your server (should be outside the directory where
the site is hosted). Your hosting control panel’s file manager should provide a way to extract the files.
Or, if you have terminal access to your hosting server (running Linux), you can use a command like:

183
CHAPTER 13. 安全和维护 13.5. UPDATING THE CORE SOFTWARE

tar -xzf drupal -8.3.2. tar.gz

9. You can also use Drush to download the archive and extract it in one step, by navigating to the temporary
directory on the server and entering this command:
drush dl drupal

10. In your site hosting directory, delete the core and vendor directories, and all files that are not in a
subdirectory, including .htaccess, composer.json, and autoload.php. Don’t delete custom and customized
files because you may end up losing the custom functionality stored in them.
11. Copy the core and vendor directories and the non-custom/non-customized files that you deleted in the
preceding step from the temporary directory to your site directory.
12. Run the update.php script using either of the following:
• Visit http://www.example.com/update.php in your browser (where www.example.com is your site’s
URL). Click Continue in the first screen to run the updates and successfully complete the script.
• Run the following Drush command: drush updb
13. If you get any error or warning, re-run the update.php script again till all the updates have been completed
successfully.
14. Open settings.php (/sites/default/settings.php) in a text editor. Find the line with the $settings[update_free_access]
variable and update it to ”FALSE”:
$settings [' update_free_access '] = FALSE;

15. Click Administration pages to return to the administration section of your site.
16. Take your site out of maintenance mode. See Section 11.2, “Enabling and Disabling Maintenance Mode”
.
17. Clear the cache. See Section 12.2, “Clearing the Cache”.
18. Re-enable any caching technique you disabled at Step 3.
19. You should have the updated version running. You can verify the current version of your software by
checking the Status report (see Section 12.5, “Concept: Status Report”).

Expand your understanding

• Section 3.2, “Concept: Additional Tools”
• Section 11.8, “Making a Development Site”
• Section 12.3, “Concept: Data Backups”

Related concepts
Section 12.5, “Concept: Status Report”

Additional resources
• ”Drupal Core Downloads” page on Drupal.org
• ”Registry Rebuild” page on Drupal.org
• The file /core/UPDATE.txt within your installation.
Attributions
Written and edited by Surendra Mohan, Boris Doesborgh, and Jojy Alphonso at Red Crackle.

184
CHAPTER 13. 安全和维护 13.6. UPDATING A MODULE

13.6 Updating a Module

Goal
Update a contributed module and run the Database updates script.

Prerequisite knowledge
• Section 13.3, “Concept: Security and Regular Updates”
• Section 13.1, “Concept: Cron”

Site prerequisites
• A contributed module has been installed and there is an update available for it. See Section 11.3,“Down-
loading and Installing a Module from Drupal.org”and Section 13.4, “Keeping Track of Updates”.
• If your site is live, you should test this process in a development environment before running it on your
production site. See Section 11.8, “Making a Development Site”.
• You have created a full-site backup. See Section 12.3, “Concept: Data Backups”.
• If you want to use the user interface, the core Update Manager module must be installed. See Section 4.3,
“Installing a Module”for instructions on installing core modules.

• If you want to use Drush, Drush must be installed. See Section 3.2, “Concept: Additional Tools”.

Steps
Before you start, check for module-specific update instructions. This is typically necessary while updating
modules that involve the usage of third-party libraries. Read and understand all module-specific requirements
before proceeding with the updates. To find instructions, check the module’s project page Read Documentation
link.
To view further instructions, download the tar.gz or .zip file from the project page to your local computer.
Unzip the file and look for README.txt, INSTALL.txt, and UPGRADE.txt that come with the module’s
installation file. Also, review the release notes on the project page by clicking the version number you’re
downloading.

You can use the administrative interface or Drush to update a contributed module. If you are updating a
custom module rather than a contributed module, if you see a message saying Installing modules and themes
requires FTP access to your server, or if the steps below do not work to obtain the new module files, follow the
steps in Section 11.6, “Manually Downloading Module or Theme Files”. You can then continue here with
step 6 in the instructions for the administrative interface below.

185
CHAPTER 13. 安全和维护 13.6. UPDATING A MODULE

Using the administrative interface

1. Put your site in maintenance mode. See Section 11.2, “Enabling and Disabling Maintenance Mode”.

2. In the Manage administrative menu, navigate to Reports > Available updates > Update (admin/report-
s/updates/update).
3. Find and check the module in the list. Click Download these updates for the module.

4. Click Continue.
5. Click Run database updates. If you obtained the new module files manually, start with this step, and reach
the database updates page by typing the URL example.com/update.php in your browser.
6. Click Continue and apply all updates. The database update scripts will be executed.

7. Click Administration pages to return to the administration section of your site.

8. Take your site out of maintenance mode. See Section 11.2, “Enabling and Disabling Maintenance Mode”
.
9. Clear the cache (refer to Section 12.2, “Clearing the Cache”).

Using Drush
1. Find the project name for the module you wish to update. It is the last segment of the module’s project
page URL. For example, if the project URL is https://www.drupal.org/project/admin_toolbar, the project
name is ”admin_toolbar”.
2. Run the following Drush command, giving the project name (for example, admin_toolbar) as a parameter
(if you have more than one module to update, add the additional module project names to the end of the
command, separated by spaces):
drush up admin_toolbar

3. Follow the instructions on the screen.

Expand your understanding

• Review the site log (refer to Section 12.4, “Concept: Log”) once the updates are complete to check for
errors.
• Section 13.7, “Updating a Theme”

186
CHAPTER 13. 安全和维护 13.7. UPDATING A THEME

Additional resources
Drupal.org community documentation page ”Updating modules”
Attributions
Adapted by Boris Doesborgh, and Sarah German at Advomatic, from ”Updating modules”, copyright 2000-
2017 by the individual contributors to the Drupal Community Documentation.

13.7 Updating a Theme

Goal
Update a contributed theme on your site and run the Database Updates script.

Prerequisite knowledge
• Section 13.3, “Concept: Security and Regular Updates”
• Section 13.1, “Concept: Cron”

Site prerequisites
• A contributed theme has been installed and there is an update available for it. See Section 11.5, “Down-
loading and Installing a Theme from Drupal.org”and Section 13.4, “Keeping Track of Updates”.
• If your site is live, you should test this process in a development environment before running it on your
production site. See Section 11.8, “Making a Development Site”.
• You have created a full site backup. See Section 12.3, “Concept: Data Backups”.
• If you want to use the user interface, the core Update Manager module must be installed. See Section 4.3,
“Installing a Module”for instructions on installing core modules.

• If you want to use Drush, Drush must be installed. See Section 3.2, “Concept: Additional Tools”.

Steps
You can use the administrative interface or Drush to update a contributed theme. If you are updating a custom
theme rather than a contributed theme, if you see a message saying Installing modules and themes requires
FTP access to your server, or if the steps below do not work to obtain the new theme files, follow the steps
in Section 11.6, “Manually Downloading Module or Theme Files”, and then continue with step 6 in the
instructions for administrative interface below.

Using the administrative interface

1. Put your site in maintenance mode. See Section 11.2, “Enabling and Disabling Maintenance Mode”.

2. In the Manage administrative menu, navigate to Reports > Available updates > Update (admin/report-
s/updates/update).
3. Find and check the theme in the list. Click Download these updates for the theme.

187
CHAPTER 13. 安全和维护 13.7. UPDATING A THEME

4. Click Continue.
5. Click Run database updates. If you obtained the new theme files manually, start with this step, and reach
the database updates page by typing the URL example.com/update.php in your browser.
6. Click Continue to run the updates. The database update scripts will be executed.
7. Click Administration pages to return to the administration section of your site.
8. Take your site out of maintenance mode. See Section 11.2, “Enabling and Disabling Maintenance Mode”
.
9. Clear the Drupal cache (refer to Section 12.2, “Clearing the Cache”).

Using Drush
1. Find the project name for the theme you wish to update, which is the last segment of the theme’s project
page URL. For example, if the project URL is https://www.drupal.org/project/mayo, the project name is
”mayo”.
2. Run the following Drush command, giving the project name (for example, mayo) as a parameter:
drush up mayo

3. Follow the instructions on the screen.

Expand your understanding

• Review the site log, see Section 12.4,“Concept: Log”, once the updates are complete to check for errors.
• Section 13.6, “Updating a Module”

Attributions
Written by Boris Doesborg.

188
Chapter 14

结语

14.1 Connecting with the Community

Prerequisite knowledge
Section 1.6, “概念：Drupal 项目”

How can you connect with the community?

The Drupal project has a world-wide community of developers and users. One of the best ways to improve
your knowledge of the platform is to connect with others that are using it, and get involved in the open-source
community. There are many ways that you can get started:
Attend an event There are both regional and international Drupal events held around the world. See the
”DrupalCon” page on Drupal.org to find international events, and the ”Event Calendar” on groups.drupal.org
or drupical.com to find regional events.
Join a local group There are Drupal user groups all around the world. Many of them have regular meetings,
which you can attend to learn more about Drupal and connect to other Drupal users. Find local user
groups on groups.drupal.org.
Participate in a topical or language group There are also interest groups for a wide range of topics,
which have on-line discussion forums. Find topical groups on groups.drupal.org. Many languages have
their own websites too; you can find them on the ”Language-specific communities” page on Drupal.org.

Chat online The Drupal project uses IRC for on-line chatting. There are regional, topical, and general-
purpose chat groups available. Find out more on the ”IRC” page on Drupal.org.
Report a problem See below.
Contribute You can contribute your time and expertise to the community in many ways, such as:

• Developing modules or themes. See the ”Contribute to Development” page on Drupal.org, or im-
proving them (using the issue queues for existing projects).
• Translating the user interface. See localize.drupal.org.
• Writing documentation. See ”Contribute to Documentation” on Drupal.org.
• Answer Support questions. See Section 14.2, “Getting Support”.

189
CHAPTER 14. 结语 14.2. GETTING SUPPORT

How can you report a problem or suggest a feature?

Each project within the community (such as the Drupal Core project for the base software, and projects for
each contributed theme and module) uses issues to keep track of software bugs and plans for new features. You
can participate by creating a bug report when you find a problem, creating a feature request, or commenting
on existing issues. Search before creating an issue, to make sure that the problem or feature has not already
been reported or requested. See the Drupal.org page ”Use the issue queue” and the Drupal.org page ”Reporting
a problem” for more information.
If you find a problem that you believe is related to security, such as a cross-site scripting vulnerability, do
not report it in the standard issue queue. Instead, report it to the security team. See the Drupal.org page ”How
to report a security issue” for details.

Related topics
Section 14.2, “Getting Support”

Additional resources
• ”Code of Conduct” on Drupal.org

• ”Event Calendar” on groups.drupal.org or drupical.com

• ”Where is the Drupal Community?” page on Drupal.org
• groups.drupal.org

• ”IRC” page on Drupal.org

• ”Ways to get involved” page on Drupal.org
• Drupal.org page ”Why get involved?”
• Drupal.org page ”Contributor tasks”

• Drupal.org page ”Use the issue queue”

• Drupal.org page ”Reporting a problem”
• Drupal.org page ”How to report a security issue”

Attributions
Written by Jennifer Hodgdon, and Joe Shindelar at Drupalize.Me.

14.2 Getting Support

Prerequisite knowledge
• Section 1.6, “概念：Drupal 项目”

• Section 14.1, “Connecting with the Community”

Where can you find support?

The Drupal project is open-source, so if you have questions about or problems with the software, your options
for finding answers and fixes are somewhat different from what they would be for commercial software.
There are several options for free support provided by community volunteers. First, some IRC channels,
local groups, and language communities encourage support questions, through on-line chat, in-person meetings,
or websites (find out more about these on Section 14.1, “Connecting with the Community”).

190
CHAPTER 14. 结语 14.3. LEARNING MORE

Second, some (but not all) contributed module, distribution, and theme projects encourage you to post
support requests in issues. Generally, projects that have a very large number of users do not allow support
requests in their issues (Drupal Core is in that category), while projects with a smaller number of users welcome
the occasional support question. Be respectful of developer time and read the documentation for the project
before posting a question in an issue. On the other hand, all projects encourage you to use issues to report
problems and bugs; see Section 14.1, “Connecting with the Community”to learn more about that.
In addition to those resources, the following sites provide free forums where volunteers answer support
questions about Drupal:
• The Drupal.org Forums
• ”Drupal Answers” on StackExchange
If you prefer to pay for support (presumably in exchange for more extensive service or better availability),
you can find service providers in the ”Drupal Marketplace” on Drupal.org.

Related topics
• Section 14.3, “Learning More”

• Section 14.1, “Connecting with the Community”

Additional resources
• ”Support” page on Drupal.org
• ”Drupal Marketplace” on Drupal.org
• The Drupal.org Forums
• ”Drupal Answers” on StackExchange

Attributions
Written by Jennifer Hodgdon.

14.3 Learning More

Prerequisite knowledge
• Section 1.6, “概念：Drupal 项目”

• Section 14.1, “Connecting with the Community”

Where can you go to learn more?

The following resources should prove useful to you, as you continue to advance your skills:
”Drupal Community Documentation” section on Drupal.org Wiki-like documentation contributed by
the Drupal community, ranging from basic to advanced, about all aspects of Drupal (site building and
administration, theming, development, and contributed modules).
api.drupal.org Reference documentation for programmers about the Drupal API.

”Drupal Planet” page on Drupal.org An aggregation of blog posts about Drupal from around the web,
posted by blogging members of the Drupal community who have applied for inclusion. Topics range from
programming to site building to Drupal news.
Groups, events, and meetups See Section 14.1,“Connecting with the Community” for more about topical,
regional, and language groups, as well as local, regional, and international events.

191
CHAPTER 14. 结语 14.3. LEARNING MORE

”Training Marketplace” page on Drupal.org The Marketplace lists paid training providers. For free
training, check whether events include training sessions; there are also free or very low-cost training
events listed on the ”Global Training Days” page on Drupal.org.
Support sites See Section 14.2, “Getting Support”to locate support forums; searching them can be useful
for learning about specific topics.
Attributions
Written by Jennifer Hodgdon, and Joe Shindelar at Drupalize.Me.

192
Chapter 15

词汇表

Ajax
A web technology used to exchange data with a server to dynamically update parts of a web page (for
example, forms) without needing entire page reloads.
Alias
A user-friendly name to replace the internal path that the system assigns to a URL on the site. For exam-
ple, you might assign an alias of /about to the About page on your site, to replace the internal path /node/5.
This would give the page a URL of http://example.com/about instead of http://example.com/node/5. See
Section 5.1, “Concept: Paths, Aliases, and URLs”for more information.
Anonymous
A person (user) interacting with the site who is not logged in. See Section 7.1, “概念：用户，角色和权
限”for more information.
Block
A chunk of content (text, images, links, etc.) that can be displayed on a page of a site. Blocks are
displayed in regions. See Section 8.1, “Concept: Blocks”for more information.
Breakpoint
Breakpoints are used to separate the height or width of browser screens, printers, and other media out-
put types into steps. A responsive site adjusts its presentation at these breakpoints. See Section 6.14,
“Concept: Responsive Image Styles”for more information.
Bundle
Synonym for Entity subtype.
Cache
The site’s internal cache stores the output of time-consuming calculations, such as computing output
for an HTML page request, and then retrieves them instead of recalculating the next time they are
needed. External caching systems can also be used on the web server to speed up a site’s response. See
Section 12.1, “Concept: Cache”for more information on the internal cache.
CMS
Acronym for Content Management System.
Configuration
Information about your site that is not content, and is meant to be more permanent than state information,
such as the name of your site, the content types and views you have defined, etc. See Section 1.5,“Concept:
Types of Data”for more information.
Content
Information meant to be displayed on your site, such as text, images, downloads, etc. See also Configura-
tion and State. See Section 1.5, “Concept: Types of Data”for more information.

193
CHAPTER 15. 词汇表

Content item
An item of content that is typically meant to be displayed as the main content of a page on your site.
This is an entity type. See Section 2.3, “Concept: Content Entities and Fields”for more information.
Content Management System (CMS)
A collection of tools designed to allow the creation, modification, organization, search, retrieval and
removal of information on a website. See Section 1.1, “概念：Drupal 作为一个内容管理系统”for more
information.
Content type
An entity subtype for the content item entity type. Each content type is used for some particular purpose
on the site, and each has its own fields. For example, a site for a farmers market might have a content
type for simple pages, and another for a vendor listing page. See Section 2.3,“Concept: Content Entities
and Fields”for more information.
Contextual link
A link to an administrative page for editing or configuring a feature of the site, shown in the context
where that feature is displayed. Example: a link to configure a menu that is shown when you hover your
mouse over the menu. See Section 4.1, “Concept: Administrative Overview”for more information.
Contributed
Modules, themes, and distributions that are not part of the Drupal core download, and that can be
downloaded separately from the Drupal.org website.
Cron
On some operating systems, cron is a command scheduler application that executes commands or scripts
periodically. Your site defines periodic tasks, also known as cron tasks, that need to be triggered either by
an operating system cron scheduler, or internally. See Section 13.1,“Concept: Cron”for more information.

Distribution
A single download that provides a shortcut for setting up a specific type of site, such as a website for
a club or for e-commerce. A distribution contains Drupal core, along with contributed modules and/or
themes; many distributions also pre-configure the site or even create sample content upon installation.
See Section 1.4, “Concept: Distributions”for more information.
Drupal core
The files, themes, profiles, and modules included with the standard project software download. See
Section 1.1, “概念：Drupal 作为一个内容管理系统”for more information.
Entity
An item of either content or configuration data, although in common usage, the term often refers to
content entities. Examples include content items, custom blocks, taxonomy terms, and definitions of
content types; the first three are content entities, and the last is a configuration entity. See also Entity
type, Entity subtype, and Field. See Section 2.3, “Concept: Content Entities and Fields”for more
information.
Entity subtype
Within a content entity type, a grouping of entities that share the same fields. For example, within
the content item entity type, a farmers market site might have subtypes (known as content types) for
static pages and vendor pages, each with its own group of fields. You may also see the term bundle used
(especially in programmer documentation) as a synonym of entity subtype. See Section 2.3, “Concept:
Content Entities and Fields”for more information.
Entity type
The overall type of an entity; in common usage, it is only applied to a content entity. Examples include
content types, taxonomy terms, and custom blocks. See Section 2.3, “Concept: Content Entities and
Fields”for more information.

194
CHAPTER 15. 词汇表

Field
Data of a certain type that is attached to a content entity. For instance, on a farmers market site’s
vendor content type, you might have fields for an image, the vendor description, and a taxonomy term.
See Section 2.3, “Concept: Content Entities and Fields”for more information.
Field bundle
Synonym for Entity subtype.
Field formatter
Configuration that defines how the data in a field is displayed. For example, a text field could be displayed
with a prefix and/or suffix, and it could have its HTML tags stripped out or limited. See also View mode
and Field widget. See Section 6.10, “Concept: View Modes and Formatters”for more information.
Field widget
Configuration that defines how someone can enter or edit data for a field on a data entry form. For
example, a text field could use a single-line or multi-line entry box, and there could be a setting for the
size of the box. See also Field formatter. See Section 6.8, “Concept: Forms and Widgets”for more
information.
Formatter
See Field formatter.
FOSS
Acronym for Free and Open Source Software, meaning software that is developed by a community of
people and released under a non-commercial license. See also GPL. See Section 1.6, “概念：Drupal 项
目”for more information.
GPL
Acronym for the GNU General Public License, a non-commercial software license. All software downloaded
from the Drupal.org website is licensed under the ”GNU General Public License, version 2”. See also FOSS.
See Section 1.7, “Concept: Drupal Licensing”for more information.
Image style
A set of processing steps that transform a base image into a new image; typical processing includes scaling
and cropping. See Section 6.12, “Concept: Image Styles”for more information.
LAMP
Acronym for Linux, Apache, MySQL, and PHP: the software on the web server that the scripts commonly
run on (although it can use other operating systems, web servers, and databases). See Section 3.1, “概
念：服务器要求”for more information.
Log
A list of recorded events on the site, such as usage data, performance data, errors, warnings, and opera-
tional information. See Section 12.4, “Concept: Log”for more information.
Menu
A set of links used for navigation on a site, which may be arranged in a hierarchy. See Section 5.6,
“Concept: Menu”for more information.
Module
Software (usually PHP, JavaScript, and/or CSS) that extends site features and adds functionality. The
Drupal project distinguishes between core and contributed modules. See Section 1.2, “概念：模块”for
more information.
Path
The unique, last part of the internal URL that the system assigns to a page on the site, which can be
a visitor-facing page or an administrative page. For example, the internal URL for the About page on
your site might be http://example.com/node/5, and in this case, the path is node/5. See also Alias. See
Section 5.1, “Concept: Paths, Aliases, and URLs”for more information.

195
CHAPTER 15. 词汇表

Permission
The ability to perform some action on the site, such as editing a particular type of content, or viewing
user profiles. See also Role. See Section 7.1, “概念：用户，角色和权限”for more information.
Reference field
A field that represents a relationship between an entity and one or more other entities, which may be the
same entity type or a different type. For example, on a farmers market site, a recipe content item might
have a reference field to the vendor (also a content item) that posted the recipe. Taxonomy term fields
are also reference fields. See Section 6.4, “Concept: Reference Fields”for more information.
Region
A defined area of a page where content can be placed, such as the header, footer, main content area,
left sidebar, etc. Regions are defined by themes, and the content displayed in each region is contained in
blocks. See Section 2.1, “Concept: Regions in a Theme”for more information.
Responsive
A site or theme is said to be responsive if it adjusts its presentation in response to the size of the browser
screen, printer, or other media output type. See also Breakpoint. See Section 6.14,“Concept: Responsive
Image Styles”for more information.
Revision
A record of the past or present state of a content entity, as it is edited over time. See Section 2.6,
“Concept: Editorial Workflow”for more information.
Role
A named set of permissions that can be applied to a user account. See Section 7.1, “概念：用户，角色
和权限”for more information.
Security update
An update that fixes a security-related bug, such as a hacking vulnerability. See Section 13.3, “Concept:
Security and Regular Updates”for more information.
State
Information of a temporary nature about the current state of your site, such as the time when cron was
last run, etc. See also Content and Configuration. See Section 1.5, “Concept: Types of Data”for more
information.
Taxonomy
The process of classifying content. See Section 6.5, “Concept: Taxonomy”for more information.
Taxonomy term
A term used to classify content, such as a tag or a category. See also Vocabulary. See Section 6.5,
“Concept: Taxonomy”for more information.
Text format
Configuration that defines the processing that happens to user-entered text before it is shown in the
browser. This might include stripping or limiting HTML tags, or turning URLs into links. See Sec-
tion 6.15, “Concept: Text Formats and Editors”for more information.
Theme
Software and asset files (images, CSS, PHP code, and/or templates) that determine the style and layout
of the site. The Drupal project distinguishes between core and contributed themes. See Section 1.3, “概
念：主题”for more information.
UI
Acronym for User Interface.
Update
A newer version of your site’s software, either Drupal core or a module or theme. See also Security
update. See Section 13.3, “Concept: Security and Regular Updates”for more information.

196
CHAPTER 15. 词汇表

User
A person interacting with the site, either logged-in or anonymous. See Section 7.1, “概念：用户，角色
和权限”for more information.
User interface
The text, styles, and images that are visible on a site, separated logically into the user interface for site
visitors and the administrative user interface.
User one (User 1)
The initial user account that is created when you install the site (whose ID number is 1). It automatically
has all permissions, even if it is not assigned an administrative role. See Section 7.2,“Concept: The User
1 Account”for more information.
View
A formatted listing of data; typically, the data comes from content entities. For example, on a farmers
market site, you might create a content item for each vendor. You could then make view that generates a
listing page that shows a thumbnail image and short description of each vendor, linking to the full-page
content item. Using the same data, you could also make a view that generates a new vendors block, which
would show information from the most recently added vendors. See Section 2.4, “Concept: Modular
Content”for more information.
View mode
A set of field formatter configuration for all of the fields of a content entity, some of which may be hidden.
Each entity subtype can have one or more view modes defined; for example, content types typically have
Full and Teaser view modes, where the Teaser view mode displays fewer or trimmed-down fields. See
Section 6.10, “Concept: View Modes and Formatters”for more information.
Vocabulary
A group of taxonomy terms to choose from when classifying content in a particular way, such as the list
of all of the vendor categories on a farmers market site. Technically, vocabularies are the entity subtype
for the taxonomy term entity type. See Section 6.5, “Concept: Taxonomy”for more information.
Widget
See Field widget.
Wizard
A web form that allows you to fill in a few values, and creates something with sensible defaults based on
the values you chose. For example, there are wizards for creating views of different types. See Section 9.3,
“Creating a Content List View”for more information.
WYSIWYG
Acronym for What You See is What You Get, meaning a method for editing content where what you see
on the editing screen closely resembles the final product. See Section 6.16, “Configuring Text Formats
and Editors”for more information.

197
Appendix A

Appendix

A.1 Guide-Wide Attributions

This guide was written by contributors to the Drupal open-source project, and is licensed under the CC BY-
SA 2.0 license. See the section called “Copyright”for more information. Details about the contributors for
guide-wide tasks are below. For individual topics, the attributions for writing, editing, and/or translating are
at the end of each topic.

Project coordination of original (English, Drupal 8) text

Writing of the initial version of this guide was coordinated by the following people:
• Amber Matz - Volunteer coordination and project management
• Jennifer Hodgdon - Content oversight
• Joe Shindelar - Content oversight
• Antje Lorch - Content oversight

Writing, editing, and testing of original text

The following people contributed to guide-wide writing:
• The glossary was written and adapted by Jennifer Hodgdon, with parts from ”Glossary”, ”Overview
of Configuration (vs. other types of information)”, and ”Working with breakpoints in Drupal 8”, each
copyright 2000-2017 by the individual contributors to the Drupal Community Documentation.
• The index was improved and curated by Anna van Raaphorst.
• Topic summaries were written by Jojy Alphonso at Red Crackle.
Guide-wide editing was done by the following people:
• Amber Matz at Drupalize.Me
• Anna van Raaphorst
• Antje Lorch
• Balu Ertl
• Boris Doesborg
• Charles Leverington
• chirag shah

199
APPENDIX A. APPENDIX A.1. GUIDE-WIDE ATTRIBUTIONS

• Grant Dunham

• Jennifer Hodgdon
• Joe Shindelar at Drupalize.Me
• Jojy Alphonso at Red Crackle — who copy edited the vast majority of the User Guide
• Kamal Kant Pansari at Intelliswift

• Michael Lenahan at erdfisch

• Swarad Mokal at Blisstering Solutions
The content was tested by:

• Zach Carter
• A workshop organized by the ”Spokane Drupal User Group” on groups.drupal.org, with students from
the Web Development Certificate program at Spokane Community College

Images
Most of the images in the guide are screen captures from the Drupal software, generated by software written
by Jennifer Hodgdon.
The word Drupal, the Druplicon logo (which appears as part of several images throughout the guide), and
the Drupal wordmark logo (which is part of the cover image), are registered trademarks of Dries Buytaert).
The cover image is a CC BY-SA 2.0 licensed illustration by Amanda Luker at Advomatic.
The Anytown Farmers Market logo, which appears as part of several images throughout the guide, is a CC
BY-SA 2.0 licensed illustration by Justin Harrell at Drupalize.Me.
The honey bee image, which appears as part of several images throughout the guide, is a public domain
image by John Severns at the English Wikipedia project via Wikimedia Commons.
The farm image, which appears as part of several images throughout the guide, is a public domain image
by Xianmin Chang via Wikimedia Commons.
The salad image, which appears as part of several images throughout the guide, is a public domain image
by Yinan Chen via Wikimedia Commons.
The carrot image, which appears as part of several images throughout the guide, is public domain im-
age K11611-1 by Stephen Ausmus at the Agricultural Research Service of the United States Department of
Agriculture via Wikimedia Commons.

Translation into Simplified Chinese

The Simplified Chinese translation of this guide was coordinated by:

• Qiangjun Ran

200
Index

Account setting Cache

configuring, 36 clearing, 174
Admin Toolbar module definition, 193
downloading, 152 overview, 173
installing, 152 rebuilding, 174
Administration Chatting online, 189, 190
overview, 27 CKEditor module
Administrative interface configuring, 97
using to update the core software, 183 CKEditor text editor
Administrative menu default assignment to text format, 97
overview, 27, 50 CMS (Content Management System)
Ajax definition, 193
definition, 193 CMS（内容管理系统）
Alias 概述, 1
definition, 193 Coder tool
overview, 43 overview, 16
Anonymous Color scheme
definition, 193 configuring, 38
Apache Web 服务器 Comment entity type
版本要求, 15 overview, 9
Appearance menu entry Comment module
administrative menu, 27 entity type, 9
Attributions for this document, 199 Community
Author connecting with, 189
assigning, 110 Composer tool
Automated Cron module overview, 16
configuring, 179 using to download modules, 165
overview, 179 using to download the core software, 165
using to download themes, 165
Backup Composite page
overview, 175 creating with modular content, 11
Bartik theme Configuration
configuring, 38 as a type of data, 4
regions in, 7 copying, 167
Basic page definition, 193
creating, 44 deploying, 167
Block synchronizing between development and live site,
creating, 113 170
creating from a view, 131 translating, 135, 141
definition, 193 Configuration Manager module
entity type, 9 using to synchronize the configuration between a
overview, 113 development and live site, 170
placing in a region, 115 Configuration menu entry
Breadcrumb region administrative menu, 27
overview, 7 Configuration Translation module
Breakpoint installing, 136
definition, 193 overview, 135
overview, 96 Configuring
Bug content translation, 137
reporting, 181, 189 home page, 49
Bundle site, 30
definition, 193 text format, 97
Contact form entity type

201
INDEX INDEX

overview, 9 definition, 194

Contact module downloading, 152, 160, 165
entity type, 9 evaluating, 145
Content finding, 145
adding to menu while editing, 51 installing, 152
as a type of data, 4 updating, 185
assigning author, 110 Contributed theme
backing up, 175 definition, 194
definition, 193 downloading, 157, 160, 165
displaying, 87 enabling, 157
editing, 46, 47 evaluating, 154
editing entry form, 84 finding, 154
entity type, 9 installing, 157
finding, 46 updating, 187
modular, 11 Contributing to the project, 189
translating, 135, 139 Copyright for this document, vii, 199
translation, 137 Core software
Content attributions for this document, 199 installing, 20
Content display updating, 183
changing, 87 Country setting
managing, 87 configuring, 30
Content editing form Cron command scheduler
overview, 83 definition, 194
Content entity type Cron task
overview, 9 configuring, 179
Content item definition, 194
creating, 44 overview, 179
definition, 193 Cross-site scripting (XSS)
Content list view preventing, 96
creating, 121 Custom block
Content Management System (CMS) creating, 113
definition, 193, 194 entity type, 9
Content menu entry Custom block module
administrative menu, 27 entity type, 9
Content reference field Custom menu
adding, 80 overview, 50
overview, 70 Custom theme
Content region enabling, 157
overview, 7 installing, 157
Content structure
planning, 11 Data type
Content Translation module configuration, 4
installing, 136 content, 4
overview, 135 overview, 4
Content type session, 4
adding, 57 state, 4
adding field to, 64 Database
definition, 194 backing up, 175
deleting, 62 configuring during the installation process, 20
Contextual link Deployment workflow
definition, 194 overview, 163
overview, 27 Devel tool
Contributed overview, 16
definition, 194 Development site
Contributed module making, 163

202
INDEX INDEX

overview, 163 using to update module, 185

synchronizing with live site, 170 using to update the core software, 183
Distribution using to update theme, 187
definition, 194 Dynamic Page Cache module
full-featured, 4 overview, 173
overview, 4
quick-start, 4 Editing content, 46, 47
Documentation Editor
about Drupal, 191 configuring, 97
about the Drupal API, 191 Editor module
available on drupal.org, 191 configuring, 97
contributed by the Drupal Community, 191 Editorial Workflow
Drupal Planet blog posts, 191 overview, 13
for programmers, 191 Effect
Downloading image, 92
core software, 17, 165 Email address
module, 152, 165 configuring, 30
module or theme files manually, 160 Enabling
theme, 157, 165 module, 152
Drupal Console tool theme, 157
overview, 16 Entity
Drupal core definition, 194
definition, 194 overview, 9
installing, 20 Entity reference field
preparing install, 17 adding, 80
Drupal licensing Entity subtype
overview, 6 definition, 194
Drupal project overview, 9
connecting with, 189 Entity type
Drupal training definition, 194
resources for, 191 overview, 9
Drupal user group Entity view mode
finding, 189 overview, 87
Drupal 内容管理系统 Error
服务器需求, 1 log report, 176
概述, 1 Error page
Drupal 协会 configuring, 30
overview, 5 Event
Drupal 官网 Drupal, 189
下载模块和主题, 1 Extend menu entry
Drupal 核心 administrative menu, 27
概述, 1
Farmers market
Drupal 项目
usage scenario for this document, xi
overview, 5
Feature
Drupal.org website
copying, 167
downloading and installing module from, 152
deploying, 167
downloading and installing theme from, 157
Featured regions
finding and evaluating modules on, 145
overview, 7
finding and evaluating themes on, 154
Field
Drush tool
adding to content type, 64
overview, 16
content reference, 70
using to download and install module, 152
definition, 194
using to download and install theme, 157
for adding references, 80
using to install the core software, 17
overview, 9, 83
using to uninstall module, 34
reference, 70

203
INDEX INDEX

taxonomy term reference, 70 overview, 6

user reference, 70 GPL (General Public License or GNU General Public
Field bundle License)
definition, 195 definition, 195
Field formatter overview, 6
definition, 195 Group
overview, 87 finding, 189
Field UI 模块 Guiding scenario for this document (farmers market),
概述, 2 xi
Field widget
definition, 195 Header region
Field 模块 overview, 7
概述, 2 Help menu entry
File administrative menu, 27
backing up, 175 Help region
File module overview, 7
entity type, 9 Hiawatha Web 服务器
Filter module 版本要求, 15
configuring, 97 Highlighted region
Firebug tool overview, 7
overview, 16 Home page
First day of week configuring, 49
configuring, 30 creating, 44
Footer menu HTML5 picture tag
overview, 50 and responsive images, 96
Footer regions
Image
overview, 7
resizing, 92
Form
Image effect
overview, 83
overview, 92
Form entity type
Image field
overview, 9
adding, 64
Formatter
Image module
definition, 195
creating a view, 121
overview, 87
Image style
Forum
creating, 92
user support, 190
definition, 195
FOSS (Free and Open Source Software)
overview, 92
definition, 195
responsive, 96
FOSS (自由及开放源代码软件)
In-place editor, 47
概述, 5
Installation process, 20
Free and Open Source Software (FOSS)
Installation profile, 20
definition, 195
Installer tool
Front page
running, 20
configuring, 30, 49
Installing
Full editor, 47
core software, 17
Full-featured distribution
development site, 163
overview, 4
module, 152
Functionality
staging site, 163
extending, 152
theme, 157
Git tool Interest group
overview, 16 finding, 189
Glossary, 193 Interface Translation module
GNU General Public License installing, 136
definition, 195 overview, 135
Internal Page Cache module

204
INDEX INDEX

overview, 173 Menu region

Internet Relay Chat (IRC) overview, 7
using to chat online, 189, 190 Menu UI 模块
IRC (Internet Relay Chat) 概述, 2
using to chat online, 189, 190 Metadata
creating, 73
Label Modular content
translating, 141 overview, 11
LAMP (Linux Apache MySQL PHP) Module
definition, 195 Admin Toolbar, 152
Language CKEditor, 97
adding, 136 Comment, 9
Language module Configuration Manager, 170
installing, 136 Configuration Translation, 135, 136
overview, 135 Contact, 9
Layout Content Translation, 135, 136
planning, 8 contributed, 152
Learning resource custom, 152
link to, 191 Custom Block, 9
Legal definition, 195
overview, 6 downloading, 152, 160, 165
Licensing Dynamic Page Cache, 173
overview, 6 Editor, 97
Linux Apache MySQL PHP (LAMP) enabling, 32, 152
definition, 195 evaluating, 145
Listing content File, 9
using Views module to, 121 Filter, 97
Live site finding, 145
synchronizing with development site, 170 Image, 121
Locale setting installing, 32, 152
configuring, 30 Interface Translation, 135, 136
Log Internal Page Cache, 173
definition, 195 Language, 135, 136
overview, 176 Node, 9
Logo image Taxonomy, 9
configuring, 38 uninstalling unused, 34
Update Manager, 152, 157
Maintenance mode
updating, 185
disabling, 149
User, 9
enabling, 149
Views, 121, 126, 131
overview, 149
Multilingual modules
Manage administrative menu
enabling, 136
overview, 27
installing, 136
Manually downloading module or theme files
MySQL 数据库
overview, 160
版本要求, 15
Menu
adding a link to page, 51 Navigation
administrative, 50 changing the order of menu items, 53
custom, 50 linking menu to page, 51
definition, 195 Nginx Web 服务器
footer, 50 版本要求, 15
main, 50 Node module
overview, 50 entity type, 9
user account, 50 Node 模块
Menu items 概述, 2
reordering, 53

205
INDEX INDEX

Page overview, 7
adding to menu while editing, 51 placing a block in, 115
composite, 11 primary menu, 7
Page cache secondary menu, 7
overview, 173 sidebar, 7
Path Regional setting
definition, 195 configuring, 30
overview, 43 Report
People menu entry Recent log messages, 176
administrative menu, 27 Reports menu entry
Performance administrative menu, 27
improving, 34 Resource
log report, 176 documentation and training, 191
status report, 177 Responsive
Permission definition, 196
changing, 106 Responsive image style
changing role, 108 overview, 96
definition, 195 Revision
denying, 106 definition, 196
granting, 106 overview, 13
PHP version Role
status report, 177 administrator, 101
PHP 编程语言 anonymous user, 101
版本要求, 15 authenticated user, 101
Planning changing, 108
site layout, 8 changing permission, 106
PostgreSQL 数据库 creating, 101
版本要求, 15 definition, 196
Primary menu region
overview, 7 Scenario for this document (farmers market)
Profile overview, xi
installation, 20 Secondary menu region
Published flag overview, 7
overview, 13 Security
assigning permission, 106
Quick editor, 47 cross-site scripting, 96
Quick-start distribution managing user accounts, 36
overview, 4 overview, 181
status report, 177
Reference field text format, 96
adding, 80 user account settings, 36
content, 70 user one account, 100
definition, 196 Security announcement
overview, 70 subscribing to by email, 182
taxonomy term, 70 subscribing to on Twitter, 182
user, 70 Security bug
Region reporting, 181
breadcrumb, 7 Security team
content, 7 overview, 181
definition, 196 Security update
featured, 7 applying, 185, 187
footer, 7 definition, 196
header, 7 keeping track of, 182
help, 7 Server information
highlighted, 7 status report, 177
menu, 7

206
INDEX INDEX

Session Term (taxonomy)

as a type of data, 4 fixed list, 71
Sidebar regions free tagging, 71
overview, 7 overview, 71
Site email address Term list
configuring, 30 creating, 73
Site information Terminology (Glossary), 193
status report, 177 Text format
Site layout configuring, 97
planning, 8 definition, 196
Site name overview, 96
configuring, 30 Theme
Site plan configuring, 38
content structure, 11 contributed, 157
Site slogan custom, 157
configuring, 30 definition, 196
Site tagline downloading, 157, 160, 165
configuring, 30 enabling, 157
Slogan evaluating, 154
configuring, 30 finding, 154
Software dependencies installing, 157
managing, 165 regions in, 7
Software version updating, 187
status report, 177 Time zone setting
SQLight 数据库 configuring, 30
版本要求, 15 Tool
Staging site Coder, 16
making, 163 Composer, 16
overview, 163 Devel, 16
State drupal Console, 16
as a type of data, 4 Drush, 16
definition, 196 Firebug, 16
Status report Git, 16
overview, 177 Toolbar
Structure menu entry overview, 27
administrative menu, 27 Training
Style Global Training Days, 191
image, 92 resource, 191
Support Training Marketplace, 191
finding, 190 Translating
configuration, 141
Tagline content, 139
configuring, 30 label, 141
Taxonomy overview, 135
creating, 73 view, 141
definition, 196 Troubleshooting
overview, 71 log report, 176
Taxonomy module status report, 177
entity type, 9
Taxonomy term UI (User Interface)
definition, 196 definition, 196
overview, 9 Uniform Resource Locator (URL)
Taxonomy term reference field overview, 43
adding, 80 Uninstalling
overview, 70 unused modules, 34

207
INDEX INDEX

Unpublished flag creating, 121

overview, 13 definition, 197
Update duplicating, 126
definition, 196 overview, 119
keeping track of, 182 translating, 141
overview, 181 View mode
status report, 177 definition, 197
Update Manager module overview, 87
overview, 182 Views module
using to install module, 152 adding to a view, 131
using to install theme, 157 creating a view, 121
Update status duplicating a view, 126
status report, 177 overview, 11, 119
URL (Uniform Resource Locator) Views UI 模块
overview, 43 概述, 2
URL alias Views 模块
overview, 43 概述, 2
URL field Vocabulary
adding, 64 creating, 73
Usage scenario for this document (farmers market), xi definition, 197
User overview, 9, 71
administrative, 100
configuring account setting, 36 Web installer
creating account, 103 running, 20
definition, 196 using to install the core software, 17
root, 100 Web 服务器
user one, 100 安装要求, 15
User account menu What You See Is What You Get (WYSIWYG)
overview, 50 configuring editor, 97
User group definition, 197
finding, 189 Widget
User interface definition, 195, 197
translating, 135 overview, 83
User Interface (UI) Wizard
definition, 197 definition, 197
User module WYSIWYG (What You See Is What You Get)
entity type, 9 configuring editor, 97
User one definition, 197
definition, 197
User profile entity type XSS (Cross-site scripting)
overview, 9 preventing, 96
User reference field
主题
adding, 80
核心, 3
overview, 70
概述, 3
User role
第三方, 3
changing, 108
自定义, 3
creating, 101
User 模块 内容管理系统（CMS）
概述, 2 概述, 1
User-entered content 匿名角色
filtering, 96 概述, 99
安装
View
核心软件, 15
adding block display to, 131
安装要求
and modular content, 11
PHP 编程语言, 15

208
INDEX INDEX

数据库, 15 概述, 120

概述, 15 视图关联
磁盘空间, 15 概述, 120
网络服务器, 15 视图字段
微软 IIS Web 服务器 概述, 120
版本要求, 15 视图排序标准
概述, 120
数据库 视图显示
安装要求, 15 概述, 120
权限 视图格式
概述, 99 概述, 120
核心主题 视图过滤条件
概述, 3 概述, 120
核心模块 角色
概述, 2 概述, 99
核心软件 贡献模块
安装要求, 15 概述, 2
模块
Field, 2
Field UI, 2
Menu UI, 2
Node, 2
User, 2
Views, 2
Views UI, 2
核心模块, 2
概述, 2
贡献模块, 2
注册用户
概述, 99

用户
概述, 99
用户角色
概述, 99
磁盘空间
安装要求, 15
第三方主题
概述, 3
管理用户账号
概述, 99

自定义主题
概述, 3
自由及开放源代码软件 (FOSS)
概述, 5
视图
上下文过滤, 120
关联, 120
字段, 120
排序标准, 120
显示, 120
格式, 120
组成, 120
过滤条件, 120
视图上下文过滤

209