This project is archived and is in readonly mode.
exception_notification fails with rails 3.1beta
Reported by gucki | September 25th, 2010 @ 01:00 AM
The mentioned plugin fails in AbstractController line 54 (http://github.com/rails/rails/blob/master/actionpack/lib/abstract_c...) because controller.respond_to?(:routes) is true, but controller.routes is nil.
I'm not sure if this is a big in the plugin or the condition in AbstractController should check for controller._routes too.
When I add the controller._routes condition, the plugin works fine.
Comments and changes to this ticket
-
Ryan Bigg September 27th, 2010 @ 11:20 PM
- State changed from new to incomplete
- Importance changed from to Low
Please add steps to reproduce this issue and/or a patch to fix it.
-
gucki September 30th, 2010 @ 01:32 PM
To reproduce just create a new rails app, add the exception notification middleware and raise an exception in any action.
Patch is already attached (see above).
-
gucki September 30th, 2010 @ 01:33 PM
The link above seems outdated, here's the patch again:
http://github.com/gucki/rails/commit/337ea1900827ef42696093a175ee7a... -
gucki October 8th, 2010 @ 12:10 PM
- Assigned user set to José Valim
This bug can be closed now, as it's been resolved by this commit:
http://github.com/rails/rails/commit/8f9e9118e402ea2fe1eec6fcb9a2d3... -
Rohit Arondekar October 8th, 2010 @ 12:33 PM
- State changed from incomplete to resolved
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>