I've just been doing stuff like this:
<% form_remote_for(:track, :url => track_path(:id => track.id), :method => "PUT") do |f| %>
been working fine for me:-) Tim
I've just been doing stuff like this:
<% form_remote_for(:track, :url => track_path(:id => track.id), :method => "PUT") do |f| %>
been working fine for me:-) Tim
unknown wrote: > I've just been doing stuff like this:
> <% form_remote_for(:track, > :url => track_path(:id => track.id), > :method => "PUT") do |f| %>
> been working fine for me:-) > Timhey tim thanks for the reply.
Really? Yours works. Hmmmm.
Yep, I'm using that syntax in a good number of places. It does the HTTP PUT and everything works fine.
I was under the impression that the :id assignment was implied through order. In this case there is no nesting so i figured track was assigned to id.
Sorry I'm not completely following you here, however you definitely need to pass the :id to singular_word_path() when you want to do a an update (e.g. HTTP PUT).
Im begging to think that the fact that i have the form nested in a row of a table, im getting errors there. I checked and there is a list of _method put hidden fields further up..
I haven't tried to do anything with hidden fields in this regaurd but I suspect it's throwing you off track, not really sure.
good luck Tim
I can’t get that to work for me. I 've been using the :html hash for passing the PUT method as a hidden field. I’ve found this method in the Beast forum and it seems to work. Though, it does seem like you should be able to pass the :method param and have it override POST.
Anyone else have experience with this?
Ed