Ok, so when an html is rendered and links are created, the Rails system refers to the routes.db to create the links? I understand now, I thought that the routes.db came in to play when a link was clicked on and routes.db assisted in the routing.
-- Very cool. Very interesting. Fairly frustrating that I can't get this to work the way it should...
Thanks for the lessons.
On Saturday, July 5, 2014 1:56:19 PM UTC-5, Hassan Schroeder wrote:
On Saturday, July 5, 2014 1:56:19 PM UTC-5, Hassan Schroeder wrote:
On Sat, Jul 5, 2014 at 11:46 AM, Jay Garnett <c340...@gmail.com> wrote:
> But I don't think routing is the problem. The rendered links are the
> problem as they aren't pointing to the right URL in the first place.
That *is* a routing problem.
And a quick test case using 4.0.x and 4.1.x shows different results
with that wildcard match - you'll get the URL you expect with 4.0.x.
Probably best to stop now, install 4.0.x and resume the tutorial :-)
FWIW,
--
Hassan Schroeder ------------------------ hassan.s...@gmail.com
http://about.me/hassanschroeder
twitter: @hassan
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/bf660d7e-57ed-4a3c-9f40-8897e7a07408%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
