I figured it out. I was using form_tag :action => ''update''
instead of
form_for and that was causing the update statement to be incorrectly
assembled.
Thanks anyway!!
On Apr 9, 11:38 am, Ali
<awilli...-KQhSGARDxiOeQVqA2Ba1Pg@public.gmane.org>
wrote:> I hope this will be an easy question...
>
> I''m trying to migrate from Rails 1.2 to 2.1, and I must admit, the
> routing is somewhat confusing me.
>
> When I update a form, I''m getting a routing error. ("No
route matches
> {id}") It''s because the update statement is getting assembled
> incorrectly somehow and the action is getting set to the id instead of
> "update"! I don''t understand how this is happening.
Does it have to
> do with routing?
>
> Here''s my development.log showing what I''m talking about.
>
> Parameters: {"commit"=>"Save",
>
"authenticity_token"=>"5d5f2530096051f30a11d94701281b54a537a012",
> "action"=>"13",
> "adminbillingrate"=>{"rate"=>"30",
"employeetype_codeid"=>"119"},
> "controller"=>"adminbillingrates"}
>
> Any help would be appreciated as always!!
> ~Ali
--~--~---------~--~----~------------~-------~--~----~
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---