--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-ta...@googlegroups.com.
To post to this group, send email to rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/3B7C311D-8FA4-40E7-ACCB-AEC9C499F9C9%40wdstudio.com.
For more options, visit https://groups.google.com/groups/opt_out.
I need to use the model name 'Action' (which will not work in Rails 4.0.3) for business reasons (it's a product name). If I name the actual model something else, is there any way to (maybe with mod_rewrite) make the URL appear the way I need it to while keeping everything working in Rails?
I've tried using the controller flag in routes.rb to try to fix this, and it seems to work, but causes a lot of problems elsewhere -- basically anything where I use the automatic URLs, like
link_to 'Link text', @instance_var
Thanks, I tried that first, and couldn't get the forms to work. What did work was this (although it's quite a hack, routes-wise):
On Mar 5, 2014, at 6:40 AM, Frederick Cheung wrote:
>
>
> On Wednesday, March 5, 2014 7:02:34 AM UTC, Walter Lee Davis wrote:
> I need to use the model name 'Action' (which will not work in Rails 4.0.3) for business reasons (it's a product name). If I name the actual model something else, is there any way to (maybe with mod_rewrite) make the URL appear the way I need it to while keeping everything working in Rails?
>
> I've tried using the controller flag in routes.rb to try to fix this, and it seems to work, but causes a lot of problems elsewhere -- basically anything where I use the automatic URLs, like
>
> link_to 'Link text', @instance_var
>
>
> resources :foos, :as => :action ?
>
resources :fw_actions :as => :action
resources :fw_actions
The second line was required in order to support POST and PUT and DELETE, so I may go through these and put :only => [:post, :put, :delete] on the latter, and :without on the former.
I couldn't find any way to have form_for work in the absence of that duplicate set of routes.
Walter
> Fred
>
>
> --
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-ta...@googlegroups.com.
> To post to this group, send email to rubyonra...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/af8c8dd9-dde6-4d15-aca2-1de45a2666a7%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-ta...@googlegroups.com.
To post to this group, send email to rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/C70782AC-EFC0-4F09-9927-C5A4AB45E57A%40wdstudio.com.
For more options, visit https://groups.google.com/groups/opt_out.