mattn wrote: > I'm just getting started with Rails 2. Plus, it's been a while since I > played with Rails at all. So to explore, I whipped out an old Rails > tutorial (from an O'Reilly book) and started going through it, to > refresh my memory.
Do not use old Rails tutorials with new versions of Rails. Do not use old versions of Rails for new projects... [...] > But here's the weird part. I then *deleted* the map.resources line > from routes.db, and my app nevertheless continued working. If you are using a version of Rails before 2.3, you need to restart the server for routing changes to take effect. > I can rake > routes and sure enough only the default routes are in force. Right, because rake loads a new instance of the Rails environment, and so it picks up the changes in the routes file. > So it > looks like maybe this a bug in Rails, where it takes some manual > jiggering to get the default routes operating properly? Anyway I > figure this must be well known, so maybe someone could just explain it > to me? No big deal, but I like to understand what's going on, if > possible - thx - m. No bug. No manual jiggering. Your routes file just got out of sync with what the server already had in memory. Best, - Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
