Ok, and the order is what?
I thought about that, by even taking this.
<cfset addCourse(pattern="/:year/:month/:day?/:blogTitle?", handler=“blog”, action=“entryDisplay” )>
<cfset addCourse(":handler/:action?/:id?")>
And making it
<cfset addCourse(":handler/:action?/:id?")>
<cfset addCourse(pattern="/:year-numeric/:month-numeric/:day-numeric?/:blogTitle?", handler=“blog”, action=“entryDisplay” )>
But no go, it still evaluates to what I reported. So if I am doing something wrong could you elaborate some more please. From what I can tell, the correct handler is being called, because they are 2 separate handlers and only one has the /:year handler with a dump and abort in it.
This tells me that it is being matched fine, it is when it gets the data out of the url that seems to be the problem. So if I make the :year as :year-numeric the correct values disappear and I get garbage as discussed earlier.
It has me confused, because I could not find anything about the order in which they run. For example is top down, as in the above examples or bottom up? You’re explanation tells me bottom up, if the default ones are run first. Just couldn’t decipher that information out of the documentation. For your reference here is the bottom of the routes file as it stands right now. Which works, and if I am understanding you right. I should take the course for year, month and day to below the standard courses. Which goes against the comments in the file.
So the order in this case? Is it bottom up? This is as I think the one area I fully can’t seem to grasp.
<cfset addCourse( pattern="/account/:action/:username/:password", handler=“account”, action=“doLogin”) />
<cfset addCourse( pattern="/admin/", handler=“admin”, action=“view”) />
<cfset addCourse(pattern="/:year/:month/:day?/:blogTitle?", handler=“blog”, action=“entryDisplay” )>
<cfset addCourse(":handler/:action?/:id?")>