Re: [Rails] Save and delete buttons: POST vs. proximity dilemma
by Markus other posts by this author
Aug 30 2005 9:26PM messages near this date
Re: [Rails] Save and delete buttons: POST vs. proximity dilemma
|
[Rails] Re: Save and delete buttons: POST vs. proximity dilemma
Have you considered using CSS (or even AJAX) to put them where you want
them?
On Sun, 2005-08-28 at 13:20, Michael Schuerig wrote:
> I'm in a dilemma: In order to keep GET requests from deleting objects,
> I'd like to use the button_to helper to get "something" that generates
> a POST request. Unfortunately, that something is a form and forms can't
> be nested.
>
> I'd also like to place buttons related to the same form close to each
> other. At the top are some navigational buttons (links), then comes the
> delete button somewhere in the middle, at the bottom is the save
> button. Achieving this without having all of these buttons in the same
> form doesn't appear to be possible.
>
> Has anyone managed to solve this?
>
> The best idea I have right now is to use submit buttons in the same
> single form, but differentiate them by name. Then, in a before_filter,
> I could redirect the delete to the actual delete action. I can't say
> that this feels good.
>
> Michael
_______________________________________________
Rails mailing list
Rails@[...].org
http://lists.rubyonrails.org/mailman/listinfo/rails
Thread:
Michael Schuerig
Justin Forder
Tom Reinhart
Markus
Michael Schuerig
rails
Steve Downey
Michael Schuerig
Jarkko Laine
|