I''ve been trying this routing pattern, but keep getting a failure to recognize it. map.connect ''/doc/:doc/:controller/:id/:action'' For a url that looks like 127.0.0.1:3000/doc/1/section/2/add I must be missing something, but none of the docs I''ve read really explain how the url is parsed. The idea is to get access to an object that contains other objects. In this example, we''ve got a document that contains sections and potentially other things with their own controller. Anyone care to shed some light on this?
What''s the error you''re getting? We did some funny routing lately and it''s been working ok. Maybe''s the order of your placement? There is a section no routing in the Agile Web Dev book, by the way. /sh Kevin Olbrich wrote:> I''ve been trying this routing pattern, but keep getting a failure to > recognize it. > > map.connect ''/doc/:doc/:controller/:id/:action'' > > For a url that looks like > > 127.0.0.1:3000/doc/1/section/2/add > > I must be missing something, but none of the docs I''ve read really explain > how the url is parsed. > > The idea is to get access to an object that contains other objects. In this > example, we''ve got a document that contains sections and potentially other > things with their own controller. > > Anyone care to shed some light on this? > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > lists.rubyonrails.org/mailman/listinfo/rails >-- Shawn Liu / Iridesco, Inc. / 212.226.4160 / 212.226.4161 fax