For what it's worth I am witrh Colin on this but this is covered in the foot note on page 46 of the pdf
6. If instead you see a message to the effect of No route matches "/say/hello", try stopping and restarting your server, because something you have done caused Rails to cache your configuration information before the controller was created. The point made on the page you are talking about (p159 on the pdf) I guess is a hang over from previous vewrsions of the book that dealt with old versions of rails but it's a good lesson to learn. Always restart your server if you get unexpected results and after making a lot of changes. It takes no time to do and can save a lot of heartache trying to debug code that has no bugs! -- 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 -~----------~----~----~----~------~----~------~--~---
