Answers.Body: <p>Sort order matters, move the more specific route up and you should be good. Alternativly set it up in routes.php using some regular expressions.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-12T23:23:41.680Z
Answers.Text: Ah! That actually makes sense when I think about it, working now ... thanks!
Answers.UserDisplayName: Rob
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-12T22:13:08.190Z
Answers.LastActivityDate: 2015-10-12T22:13:08.190Z
Answers.UserDisplayName: carlcs
Body: <p>I have a dynamic route for individual user <code>/profiles</code>. I expected it would be possible to override this route for <code>/profiles/all</code> but apparently not.</p>
  
  <p>This can be achieved in the template I expect, with a conditional statement on the url <code>.segment(2)</code>, but it would save a little time if it was possible to override a wildcard route.</p>
  
  <p><a href="https://i.sstatic.net/fU73G.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/fU73G.png" alt="enter image description here"></a></p>
  
Tags: <templating><url><routes><routing><segments>
Title: Override a wildcard dynamic route template
ThreadText: # Override a wildcard dynamic route template
  
  (Asked by: username_0 on 2015-10-12)
  
  I have a dynamic route for individual user `/profiles`. I expected it would be possible to override this route for `/profiles/all` but apparently not.
  
  This can be achieved in the template I expect, with a conditional statement on the url `.segment(2)`, but it would save a little time if it was possible to override a wildcard route.
  
  [![enter image description here](https://i.sstatic.net/fU73G.png)](https://i.sstatic.net/fU73G.png)
  
  **Tags:** templating, url, routes, routing, segments
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-10-12. Score: 3 | Accepted answer
  
  Sort order matters, move the more specific route up and you should be good. Alternativly set it up in routes.php using some regular expressions.
  
  > **Comments:**
  > **username_0**: Ah! That actually makes sense when I think about it, working now ... thanks!  
  
  ---
  
  