As a workaround to avoid hacking, you could create an add template group and let its index template handle the requests when there is no second segment. You would be able to stay DRY by embedding the actual template, with no other tags on add/index. For instance if this route goes to the template group foo and the template bar, add/index would just contain:

Only solution that works is to create &#123;embed='foo/bar'&#125; duplicates of the template to cover all routing options and then set up static routes to each. An appalling hack - given that Template Routes is supposed to be providing this (and pretty much only) this service, for it to be broken over a minimum of four point upgrades (3.1 -> 3.5) is very poor.

The existing documentation for Template Routes is pretty poor - but it might be a kindness to include somewhere within that rats-nest a very clear label saying that some of the features described therein don’t actually work, and won’t ever work in this version of EE. Would save others time I think.

Username

Password

Email Address

Used to log in

Display Name

Password

By registering, you agree to our terms of service, including receiving some tips and offers from us from time to time. We never spam, and we never share your email address with third parties. Terms of ServicePrivacy Policy