2

The variables need to have a name and that url_title is a reserved word. To avoid conflicts, if you need to keep the Segments required set to no, keep a static part on the first segment: /{coaching_type:regex[(workplace|personal)]}-coaching/{coaching_title:alpha_dash} By this way, you can't grab the first segment by {segment:coaching_type}, but {segment_1}...


2

disclaimer First things first: the documentation does not say it, but isn't advisable to use a route on the first segment. Why? I've no idea. This is something a former EllisLab developer told me. loading the entry The Template Routes mess up with the automatic discovery of entries. From the docs: Template Routes overrides the default behavior of URLs, ...


1

Surrounding each of the values with a separator, including the start and end of the index makes matching simple and ensures you match a '2' and not '22' or '212' (for example). I tend to use @ or / rather than | so that I don't need to escape the pipe in the regex. @4@4@4@4@2@2@ @9@9@9@2@2@ etc Now you can easily match a specific number with: {exp:stash:...


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