Marnen Laibow-Koser wrote in post #972921: > James Byrne wrote in post #972918:
>> >> Then does that mean one must always provide a route for the new method, >> even if it makes no sense to do so within a given context? > > I don't understand your question. > I get this error when I submit the form. no route exists for "/users/1/roles" However, I get to the form via "/users/1/roles/new" called from "/users/1/role", which is where I want to return to after the update completes. At the moment I am perplexed by this, to me, mysterious behaviour and error message. In other words, I can start by entering http://localhost:3000/users/1/roles That URL displays all the roles associated with User.find(1) >From that page I follow a link to http://localhost:3000/users/1/roles/new which displays the input form. When I complete and submit the form I get this error: No route matches "/users/1/roles" which is the very URL I have just come from. -- 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.
