4

The problem is having no rule and having alpha_dash are exactly the same thing, so the error message is correct, those are duplicate routes. If you added the :pagination rule to the {pagination} variable, then it should work: /about/news/{pagination:pagination} Also, you'll need to have the {pagination:pagination} rule first, since alpha_dash would catch ...


3

To answer this you need to think about what you want to have happen when EE sees a URL - only with this clear can you work out what the right approach would be. So with your example, it sounds like foo/bar/balloons and red/pretty/balloons should be resulting in different pages - but to know how we need to know how they differ: are they different pages, or ...


2

Well, Sean. Now, we have a problem. I already had this discussion with EllisLab, but I believe you should too. Their answer was to use something like: /about/news/{news-post:alpha_dash}/{pagination} And to set required segments to no. This way, the route will match: /about/news/{news-post:alpha_dash}/{pagination} /about/news/{news-post:alpha_dash} /about/...


2

You can start from this Mike Boyink's tutorial it is very clear and help me to understand better templates route


2

:url_title will match any string that could be a url title as it is converted to ([^/]+) [1] To stop this rule matching template groups, you can check that the match is for a real entry in the expected channel like this: ':url_title' => function($router, $wildcard) { // valid entry in the 'home' channel (id=3)? if ($wildcard->isValidUrlTitle(...


1

Whether you can depends somewhat on how your site / templates are designed. As far as EE is concerned, you don't really need to specify which channel or anything to retrieve an entry - the url_title is enough on its own. So if you want to use the url structure domain.com/url_title there is no reason why you could not do use a template design like this: {exp:...


1

You have lots of options, which is best will depend on what your site design / data looks like. The following suggestions are not in a recommended order, just trying to separate out your options: You can access the content of the first nine segments directly within EE templates via URL Segment Variables - so in your case the content of segment_1 is ...


1

This turned out to be a bug, which appears to have been around since 3.4.0. Temporary fix ℅ Ellis Labs is to replace the static segment 2 element with regex to achieve same end: no idea why it works, but it does. So, for example, to get the example route from question to work, you need to modify it as follows: /resources/{seg_2:regex[(public\-sector)]}/{...


1

I don't think you can. You also don't need to do that. The template file you are wanting to be your homepage is already called index. http://www.ee2docs.com/cp/design/templates/new_template_group.html#default-home-page Set your site template group as your default template group via this setting, and it automatically will make site/index your root.


1

Yes. Although seg2cat will make your life easier. The index template inside your template_group will catch anything (depending on your use of other add-ons such as Structure or Pages and your strict 404 settings). So in /template_group/index you want to detect the relevant elements of the URL to then deliver your entry. IMO, your URL is a bit pointless - ...


1

I was just struggling with this problem, everything I was doing was resulting in the same error. I fortunately just managed to fix it though, problem is I'm not 100% sure why it happened I just know that it did. Open up the following file: system > expressionengine > libraries > template_router and open up Route.php Find the following line of code: $hash = ...


1

I just encountered this same issue, and filed a bug report - including a fix: https://support.ellislab.com/bugs/detail/20680


Only top voted, non community-wiki answers of a minimum length are eligible