{"id":263,"date":"2013-09-23T16:41:55","date_gmt":"2013-09-23T14:41:55","guid":{"rendered":"http:\/\/hesmid.nl\/test\/?p=263"},"modified":"2013-09-24T00:26:33","modified_gmt":"2013-09-23T22:26:33","slug":"the-wordpress-template-hierarchy","status":"publish","type":"post","link":"https:\/\/hesmid.nl\/test\/the-wordpress-template-hierarchy\/","title":{"rendered":"The WordPress Template Hierarchy"},"content":{"rendered":"

http:\/\/codex.wordpress.org\/Template_Hierarchy<\/a><\/p>\n

The General Idea<\/h3>\n

WordPress uses the\u00a0Query String<\/a>\u00a0\u2014 information contained within each link on your web site \u2014 to decide which template or set of templates will be used to display the page.<\/p>\n

To see the query string put this in your theme’s page template:<\/p>\n

<?php\r\necho \"<pre>\"; print_r($wp_query->query_vars); echo \"<\/pre>\";\r\n?><\/code><\/pre>\n
WordPress matches every Query String to query types \u2014 i.e. it decides what type of page (a search page, a category page, the home page etc.) is being requested.<\/p>\n
Templates are then chosen \u2014 and web page content is generated \u2014 in the order suggested by the WordPress Template hierarchy, depending upon what templates are available in a particular WordPress Theme.<\/p>\n
WordPress looks for template files with specific names in the current Theme’s directory and uses the\u00a0first matching<\/i>\u00a0template file listed under the appropriate query section below.<\/p>\n
With the exception of the basic\u00a0index.php<\/tt>\u00a0template 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,\u00a0index.php<\/tt>\u00a0(the Theme’s home page template file) will be used.<\/p>\n
Examples<\/h3>\n
If your blog is at\u00a0http:\/\/example.com\/blog\/<\/tt>\u00a0and a visitor clicks on a link to a category page like\u00a0http:\/\/example.com\/blog\/category\/your-cat\/<\/tt>: Here is the progression of how WordPress uses the template hierarchy to find and generate the right file.<\/p>\n
WordPress looks for a template file in the current Theme’s directory that matches the category’s ID.<\/p>\n
    \n
  1. If the category’s ID is 4, WordPress looks for a template file named\u00a0category-4.php<\/tt>.<\/li>\n
  2. If it is missing, WordPress next looks for a generic category template file,\u00a0category.php<\/tt>.<\/li>\n
  3. If this file does not exist either, WordPress looks for a generic archive template,\u00a0archive.php<\/tt>.<\/li>\n
  4. If it is missing as well, WordPress falls back on the main Theme template file,\u00a0index.php<\/tt>.<\/li>\n<\/ol>\n
    Page display<\/span><\/p>\n
    Template file used to render a static page (page<\/tt>\u00a0post-type)<\/p>\n
    \n
    \n
      \n
    1. custom template file<\/tt>\u00a0– The\u00a0Page Template<\/a>\u00a0assigned to the Page. See\u00a0get_page_templates()<\/a>.<\/li>\n
    2. page-{slug}.php<\/tt>\u00a0– If the page slug is\u00a0recent-news<\/b>, WordPress will look to use\u00a0page-recent-news.php<\/tt><\/li>\n
    3. page-{id}.php<\/tt>\u00a0– If the page ID is\u00a06<\/b>, WordPress will look to use\u00a0page-6.php<\/tt><\/li>\n
    4. page.php<\/tt><\/li>\n
    5. index.php<\/tt><\/li>\n<\/ol>\n
      \"\"
      Template_Hierarchy<\/a><\/figcaption><\/figure>\n<\/dd>\n<\/dl>\n
      Using Conditional Tags<\/h3>\n
      WordPress provides more than one way to match templates to query types. WordPress Theme developers can also use\u00a0Conditional Tags<\/a>\u00a0to 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.<\/p>\n
      WordPress can load different\u00a0Templates<\/a>\u00a0for different\u00a0query<\/i>\u00a0types. There are two ways to do this: as part of the built-in\u00a0Template Hierarchy<\/a>, and through the use of\u00a0Conditional Tags<\/a>\u00a0within\u00a0The Loop<\/a>\u00a0of a template file.<\/p>\n
      To use the\u00a0Template Hierarchy<\/a>, you basically need to provide special-purpose Template files, which will automatically be used to override\u00a0index.php<\/i>. For instance, if your Theme provides a template called\u00a0category.php<\/i>\u00a0and a category is being queried,\u00a0category.php<\/i>will be loaded instead of\u00a0index.php<\/i>. If\u00a0category.php<\/i>\u00a0is not present,\u00a0index.php<\/i>\u00a0is used as usual.<\/p>\n
      You can get even more specific in the Template Hierarchy by providing a file called, for instance,\u00a0category-6.php<\/i>\u00a0— this file will be used rather than\u00a0category.php<\/i>\u00a0when generating the page for the category whose ID number is 6.<\/p>\n
      If your Theme needs to have even more control over which Template files are used than what is provided in the\u00a0Template Hierarchy<\/a>, you can use\u00a0Conditional Tags<\/a>. The Conditional Tag basically checks to see if some particular condition is true, within the\u00a0WordPress Loop<\/a>, and then you can load a particular template, or put some particular text on the screen, based on that condition.<\/p>\n
      For example, to generate a distinctive stylesheet in a post only found within a specific category, the code might look like this:<\/p>\n
      <?php\r\nif ( is_category( '9' ) ) {\r\n    get_template_part( 'single2' ); \/\/ looking for posts in category with ID of '9'\r\n} else {\r\n    get_template_part( 'single1' ); \/\/ put this on every other category post\r\n}\r\n?><\/pre>\n
      Or, using a query, it might look like this:<\/p>\n
      <?php\r\n$post = $wp_query->post;\r\nif ( in_category( '9' ) ) {\r\n    get_template_part( 'single2' );\r\n} else {\r\n    get_template_part( 'single1' );\r\n}\r\n?><\/pre>\n","protected":false},"excerpt":{"rendered":"
      http:\/\/codex.wordpress.org\/Template_Hierarchy The General Idea WordPress uses the\u00a0Query String\u00a0\u2014 information contained within each link on your web site \u2014 to decide which template or set of templates will be used to display the page. To see the query string put this in your theme’s page template: <?php echo “<pre>”; print_r($wp_query->query_vars); echo “<\/pre>”; ?> WordPress matches every […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[17],"tags":[],"acf":[],"_links":{"self":[{"href":"https:\/\/hesmid.nl\/test\/wp-json\/wp\/v2\/posts\/263"}],"collection":[{"href":"https:\/\/hesmid.nl\/test\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hesmid.nl\/test\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hesmid.nl\/test\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/hesmid.nl\/test\/wp-json\/wp\/v2\/comments?post=263"}],"version-history":[{"count":8,"href":"https:\/\/hesmid.nl\/test\/wp-json\/wp\/v2\/posts\/263\/revisions"}],"predecessor-version":[{"id":271,"href":"https:\/\/hesmid.nl\/test\/wp-json\/wp\/v2\/posts\/263\/revisions\/271"}],"wp:attachment":[{"href":"https:\/\/hesmid.nl\/test\/wp-json\/wp\/v2\/media?parent=263"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hesmid.nl\/test\/wp-json\/wp\/v2\/categories?post=263"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hesmid.nl\/test\/wp-json\/wp\/v2\/tags?post=263"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}