<p>The CP route settings don’t have a token for matching multiple URI segments. However you can pull it off from <strong>craft/config/routes.php</strong> instead:</p>

<pre class="lang-php prettyprint-override"><code>return array(
    'blog/(.+)' =&gt; 'path/to/template',
);
</code></pre>

<p>You’ll be able to access whatever was captured by <code>(.*)</code> from your templates via <code>matches[1]</code>.</p>

CC BY-SA 3.0
2015-09-13T14:39:00.180Z
2015-09-13T14:39:00.180Z
Brandon Kelly
<p>I'm setting up a route in control panel. I'd like to use a token that is similar to asterisk but involves forward slashes. Here's an example:</p>

<p>I want to route everything from site.com/blog/* to a single template.
If I route <strong>site.com/blog/some-uri-identifier</strong> , it works fine and I'm able to get <strong>"some-uri-identifier"</strong> in my template (using slug option).
I need to route <strong>site.com/blog/some/uri/identifier-long-name</strong> and still go to the same template + get <strong>"/some/uri/identifier-long-name"</strong> in it.</p>

<p>Thanks!</p>

<routes><routing>
Route token that includes forward slashes
# Route token that includes forward slashes

(Asked by: username_0 on 2015-09-13)

I'm setting up a route in control panel. I'd like to use a token that is similar to asterisk but involves forward slashes. Here's an example:

I want to route everything from site.com/blog/\* to a single template.
If I route **site.com/blog/some-uri-identifier** , it works fine and I'm able to get **"some-uri-identifier"** in my template (using slug option).
I need to route **site.com/blog/some/uri/identifier-long-name** and still go to the same template + get **"/some/uri/identifier-long-name"** in it.

Thanks!

**Tags:** routes, routing

---

## 1 answers

### Answer by username_1 on 2015-09-13. Score: 4 | Accepted answer

The CP route settings don’t have a token for matching multiple URI segments. However you can pull it off from craft/config/routes.php instead:
return array(
    'blog/(.+)' => 'path/to/template',
);

You’ll be able to access whatever was captured by (.*) from your templates via matches[1].


---

