search for: ptontig

The shift to the :has_many and :has_one options when defining nested resource routes has me perplexed. The block format allows me to define custom REST actions like publish in the example below: map.resources :users do |user| user.resources :articles, :member => { :publish => :put } end It also allows for multiple levels of nesting if necessary. What I''d really like to

In a wiki, routes are handling web_index /:web {:controller=>"wiki", :action=>"index"} web_topic /:web/:topic {:controller=>"wiki", :action=>"view"} action /:web/:topic/:action {:controller=>"wiki"} That is the default action is "view". Two questions: 1. Can I constrain the patterns allowed for