{"id":1948280,"date":"2020-10-22T07:22:12","date_gmt":"2020-10-22T11:22:12","guid":{"rendered":"https:\/\/dev.theeventscalendar.com\/knowledgebase\/?post_type=tribe-knowledgebase&p=1948280"},"modified":"2022-01-21T08:59:03","modified_gmt":"2022-01-21T13:59:03","slug":"using-the-template-management-filters","status":"publish","type":"post","link":"https:\/\/dev.theeventscalendar.com\/knowledgebase\/using-the-template-management-filters\/","title":{"rendered":"Using Template Management Filters"},"content":{"rendered":"\n

There are lots of ways to customize The Events Calendar, from minor CSS changes<\/a> to completely overriding any of the template files<\/a> with your own markup. We’re going to look at template filters- an advanced customization technique that completely bypasses the calendar’s template files, allowing you to display calendar content in any of your existing theme templates, or build your own from scratch using event data.<\/p>\n\n\n\n

Meet the Template Hierarchy (aka “Template Hijack”) filter<\/h2>\n\n\n\n

We introduced a brand new filter in The Events Calendar 5.3:<\/p>\n\n\n

\ntribe_events_views_v2_use_wp_template_hierarchy\n<\/pre><\/div>\n\n\n
With this template filter, we can tell The Events Calendar to use the WordPress template hierarchy<\/a> for events instead of its own templates.<\/p>\n\n\n\n
\"\"
In this example, events are displayed with the theme’s archive template instead of the calendar template that comes with the plugin. The calendar template is a custom archive template, but using this new filter ignores that template in favor of the WordPress template hierarchy<\/a>, forcing the calendar to behave like any other post archive.<\/figcaption><\/figure>\n\n\n\n
Basic template filte usage<\/h2>\n\n\n\n
Here’s an example of the template filter at its most basic in a theme’s functions.php<\/code> file:<\/p>\n\n\n
\nadd_filter(\n  'tribe_events_views_v2_use_wp_template_hierarchy',\n  function( $hijack, $template, $context, $query ) {\n    if ( ! is_singular() ) {\n      $hijack = true;\n    }\n\n    return $hijack;\n  },\n  10,\n  4\n);\n<\/pre><\/div>\n\n\n
There are four arguments in there, with $hijack<\/code> being the only required one. It’s a boolean that transitions the calendar from plugin templates to theme templates when set to true<\/code>.<\/p>\n\n\n\n
In this basic example, we’ve wrapped the $hijack<\/code> argument inside a condition that checks if the current view is not<\/strong> a single event post. In other words, are we looking at an event or at the calendar? If it’s not an event, then let the WordPress template hierarchy hijack the calendar and leave the individual event posts alone.<\/p>\n\n\n\n
Template filter arguments<\/h2>\n\n\n\n
We just covered the $hijack<\/code> argument, but there are three additional ones that are optional:<\/p>\n\n\n\n