On Oct 22, 12:09 pm, "Mislav Marohnić" <[EMAIL PROTECTED]> wrote: > Trevor, that's exactly what this change did. You won't be getting that error > anymore and you can safely remove "and return false" from your filters.
Terrific. This seems like a smart change to me. I dig all of the simplification and streamlining going on in this release. If that error can't occur anymore, shouldn't it be removed from Rails? I didn't see that it was taken out in the changeset linked above, which is why I'm wondering. I see a few mentions of "DoubleRenderError" in this file: http://dev.rubyonrails.org/browser/trunk/actionpack/lib/action_controller/base.rb I can open a ticket (or try to create a patch) if that's more appropriate. - Trevor --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
