What to do about this, if anything, depends, of course, on the intended audience, but if it’s ruby newbies, ….

before_filter :mark_return_point :only =>[x,z]

Which does exactly the same thing and marks a return parameter in the session, we just have a

return_to_last_point 

then whenever an action like an update completes redirects to the last point someone went through.

Not sure which I prefer, our current way keeps the logic of the flow inside the controller

<%= link_away h(person.display_name), person %>

(person also gets passed for generated delete links.)

Not really sure what the answer is, except to only use link_away for edit links.

<%= link_away 'Edit', edit_person_path(@person) %>

Will fail with the error “undefined method `symbolize_keys’ for “/people/1/edit”:String”

def link_away(name, options = {}, html_options = nil)
    link = case options
        when String
            link_to(name, options + "?return_uri=" + url_for(:only_path => true), html_options)
        else
            link_to(name, { :return_uri => url_for(:only_path => true) }.update(options.symbolize_keys), html_options)
        end
end

But that’s fairly unsatisfying, if for no reason than it will add an extra “?” to the URL if there are already parameters in it. (My Ruby-fu is weak.)

Thanks for sharing!

Yours did exactly what I wanted RIGHT AWAY. I thought something must be wrong, but nope, you’d really cleaned all that gunk while leaving the meat intact just as laid out. MANY thanks !

(Tidy refused to even try, by the way.)