action_after_update would not work either. You can override on_update.js.erb 
view if using inline form, or update_respond_to_html

El lunes, 28 de diciembre de 2015 3:10:27 (CET) Gloufy escribió:
> thank you for the reponse
> 
> i just want after a update go to another controller...
> 
> Le lundi 28 décembre 2015 10:34:58 UTC+1, Sergio Cambra a écrit :
> > action_after_update never existed, I see action_after_create useful, but
> > not
> > after update. After create, you may want to create another record so you
> > need
> > persistent, you may want to update current record so you need
> > action_after_create = :update, or nothing, so form is closed. After update
> > I
> > would think you may want to keep updating same record, so you need
> > persistent,
> > or close the form.
> > 
> > Override main_path_to_return in the controller, that's used for cancel
> > button
> > and action redirect (when form is submitted without ajax, because it's
> > open on
> > new tab or ajax is disabled).
> > 
> > El viernes, 25 de diciembre de 2015 14:44:42 (CET) Gloufy escribió:
> > > Hi,
> > > 
> > > I've got a another question :
> > > why action_after_update doesn't exists ?
> > > and how to define a custom redirection for the cancel button on form ?
> > > *thank you.*
> > > 
> > > *Gloufy*


-- 
You received this message because you are subscribed to the Google Groups 
"ActiveScaffold : Ruby on Rails Gem" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/activescaffold.
For more options, visit https://groups.google.com/d/optout.

Reply via email to