Thanks Tim, that's exactly what I was looking for. I don't disagree that messing too much with these defaults is something I'd want to do often and without reason. Effectively this is just another route to an existing action, in the same way that get :authorize. Had this not worked so easily in Rails 2 I might have opted for resources/generate and this wouldn't have been an issue :)
Cheers RobL On 11 January 2011 14:05, Tim Shaffer <[email protected]> wrote: > You're having a hard time with "create" because it's one of the default > actions (show, create, update, destroy, new, edit). There's some hard coding > in Rails that's interfering with what you're trying to do. In this case, if > the action is "create", it excludes the action from the path. > > Overriding the default actions generally isn't a good idea. That being said, > you can force rails to do what you want by forcing the path option: > > get :create, :as => :create, :path => :create > > -- > 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. > -- Rob Lacey [email protected] http://www.robl.me -- 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.
