# The Basics

When routing is enabled in the Construct Settings, there are two ways routing occurs in Construct 2.

  1. If the ExpressionEngine URI matches a Node full route
  2. If the ExpressionEngine URI matches a route in Construct’s routing config.

When a node is matched, the specified template from the Node is served. When a route config is matched, what you have specified for that route will run.

# Route Variables

Construct makes certain variables available when it matches a route or a Node.

Note

If the route is being served by the config file but does not match a node, and the values are not set by the config (where applicable), the values of these items will be set to false.

{construct_route:node_id}

The ID of the currently matched Node.

{construct_route:node_tree_id}

The ID of the Tree from the currently matched Node.

{construct_route:node_parent_id}

The parent ID of the currently matched Node. 0 if Node has no parent.

{construct_route:node_level}

The level of the currently matched Node.

{construct_route:node_name}

The name of the currently matched Node.

{construct_route:node_slug}

The slug of the currently matched node — which will be the same as the last URI segment.

{construct_route:node_external_link}

The external link field of the currently matched Node.

{construct_route:node_full_route}

The full route of the currently matched Node. Example: about/executives/ceo.

{construct_route:node_entry_id}

The entry ID of the selected entry for the currently matched Node. When using Construct to create pages, this is how you connect everything together. You can feed this tag into the entry_id parameter of an exp:channel:entries tag pair to serve the specified Node entry.

Example
												
{exp:channel:entries
	disable="categories|member_data|pagination"
	dynamic="no"
	entry_id="{construct_route:node_entry_id}"
	limit="1"
	status="open"
}
	<h1>{title}</h1>
	{body}
{/exp:channel:entries}
												
											

{construct_route:node_output}

Whether the currently matched Node is set to output in Menus.

{construct_route:node_pagination}

Whether the currently matched Node is set to paginate.

{construct_route:node_pagination_amount}

The pagination amount set for the currently matched Node.

{construct_route:node_listing_channels}

The channel(s) chosen for listing. If there is more than on channel, they will be pipe delimited.

Example
												
{exp:channel:entries
	disable="categories|member_data"
	dynamic="no"
	channel="{construct_route:node_listing_channels}"
	{if construct_route:node_pagination}
	limit="{construct_route:node_pagination_amount}"
	{if:else}
	limit="1"
	{/if}
	status="open"
}
	<h1>{title}</h1>
	{body}
{/exp:channel:entries}
												
											

# How the Extension Hook Works

The Construct extension uses the core template route hook. When you load any URI in ExpressionEngine, the core template route hook is run.

Construct checks to see if there is a Node with routing enabled that matches the current URI and has a template associated with it. It also checks to see if the route is a match for any config file routes.

Note

It is recommended that you completely disable the ExpressionEngine build-in Pages module since it also has to run queries to see if the current URI is a match for the page. The routing functionality of Construct is intended to replace the first party Pages module.

# Serving Templates

Construct can serve both regular and hidden templates, but it is recommend that you use hidden templates so they can’t be accessed directly — apart from a Construct route — and therefore serve duplicate end-points or run into errors because Construct Route Template Tags aren’t available.