-
Notifications
You must be signed in to change notification settings - Fork 88
Errship Gem Not working #45
Comments
Due to a change in the way routing is handled in Rails 3.2, we may no longer depend on rescue_from AbstractController::ActionNotFOund to catch the exception and redirect to a 404. The fix is to configure exceptions_app so that errors are also routed: https://github.com/vidibus/vidibus-routing_error#alternative-one. I can submit a patch later if this sounds good. |
I'm not well qualified to decide. Any second opinions out there? |
@mchung sure. can you submit a pull request and we'll check it out? |
@kmcurry Sorry I've been missing in action. Had a crazy holiday. Did you just close this pull request? |
yep! On Mon, Jan 7, 2013 at 9:22 AM, Ryan Castillo notifications@github.comwrote:
Kevin Curry |
Errship gem should display the correct error page when an error occurs but it's not happening
Example
If you load up http://brigade.codeforamerica.org/locations the 404 page should render but instead the default Rails 404 renders
If you go to http://brigade.codeforamerica.org/notfound then the correct 404 page shows
This also happens with 500 pages
http://brigade.codeforamerica.org/error
versus
http://brigade.codeforamerica.org/deployed_applications
Which renders the default Rails 500 page instead of the nice 500 page.
The text was updated successfully, but these errors were encountered: