Languages: English ? Fran?ais ? Italiano ? 日本語 ? ??? ? Русский ? Espa?ol ? Português do Brasil ? (Add your language)
WordPress Templates fit together like the pieces of a puzzle to generate the web pages on your WordPress site. Some templates (the header and footer template files for example) are used on all the web pages, while others are used only under specific conditions.
This article seeks to answer the following question:
Which template file(s) will WordPress use when it displays a certain type of page?
Since the introduction of Themes in WordPress 1.5, Templates have become more and more configurable. In order to develop WordPress themes, a proper understanding of the way WordPress selects template files to display the various pages on your blog is essential. If you seek to customize an existing WordPress theme, this article aims to help you decide which template file needs editing.
WordPress provides more than one way to match templates to query types. WordPress Theme developers can also use Conditional Tags to control which templates will be used to generate a certain page. Some WordPress Themes may not implement all of the template files described here. Some Themes use conditional tags to load other template files. See the Conditional Tagspage and "Query Based" in Theme Development for more information.
WordPress uses the Query String — information contained within each link on your web site — to decide which template or set of templates will be used to display the page.
First, WordPress matches every Query String to query types — i.e. it decides what type of page (a search page, a category page, the home page etc.) is being requested.
Templates are then chosen — and web page content is generated — in the order suggested by the WordPress Template hierarchy, depending upon what templates are available in a particular WordPress Theme.
WordPress looks for template files with specific names in the current Theme's directory and uses the first matching template file listed under the appropriate query section below.
With the exception of the basic index.php template file, Theme developers can choose whether they want to implement a particular template file or not. If WordPress cannot find a template file with a matching name, it skips down to the next file name in the hierarchy. If WordPress cannot find any matching template file,index.php (the Theme's home page template file) will be used.
If your blog is at http://example.com/blog/ and a visitor clicks on a link to a category page likehttp://example.com/blog/category/your-cat/: Here is the progression of how WordPress uses the template hierarchy to find and generate the right file.
WordPress looks for a template file in the current Theme's directory that matches the category's ID.
If a visitor goes to your home page at http://example.com/blog/, the following happens:
The following diagram shows which template files are called to generate a WordPress page based on the WordPress Template hierarchy.
A more in depth hierarchy diagram, including template-related conditional tags and body CSS classes, can be found here.
The following sections describe the order in which template files are being called by WordPress for each query type.
Template file used to render the Blog Posts Index, whether on the site front page or on a static page. Note: on the Site Front Page, the Front Page template takes precedence over the Blog Posts Index (Home) template.
Template file used to render the Site Front Page, whether the front page displays the Blog Posts Index or a static page. The Front Page template takes precedence over the Blog Posts Index (Home) template.
Template file used to render a single post page.
Template file used to render a static page (page post-type)
Template file used to render a Category Archive Index page
Template file used to render a Tag Archive Index page
Template file used to render the Archive Index page for a Custom Taxonomy
Template file used to render the Archive Index page for a Custom Post Type
(For rendering a single custom post type, refer to the Single Post display section above.)
Template file used to render an Author Archive Index page
Template file used to render a Date-Based Archive Index page
Template file used to render a Search Results Index page
Template file used to render a Server 404 error page
Template file used to render a single attachment (attachment post-type) page
The WordPress templates system allow you to filter the hierarchy. The filter (located in theget_query_template() function) uses this filter name: "{$type}_template" where $type is the a file name in the hierarchy without the .php extension.
Full list:
For example, let's take the default author hierarchy:
To add author-{role}.php before author.php we can manipulate the actual hierarchy using the 'author_template' hook. This allows a request for /author/username where username has the role of editor to display using author-editor.php if present in the current themes directory.
function author_role_template( $templates='' ){ $author = get_queried_object(); $role=$author->roles[0]; if(!is_array($templates) && !empty($templates)) { $templates=locate_template(array("author-$role.php",$templates),false); } elseif(empty($templates)) { $templates=locate_template("author-$role.php",false); } else { $new_template=locate_template(array("author-$role.php")); if(!empty($new_template)) array_unshift($templates,$new_template); } return $templates;}add_filter( 'author_template', 'author_role_template' );
联系客服