similar to: routing error does not get caught by rescue_action_in_public

I''m using the rescue_action_in_public example from the Agile book to handle errors and email serious ones to me. In my application.rb controller: def rescue_action_in_public(exception) logger.error("rescue_action_in_public executed") case exception when ActiveRecord::RecordNotFound, ActionController::RoutingError, ActionController::UnknownAction

I''m trying to override rescue_action_in_public() using the PP example, but my application hangs every time I generate an error. def rescue_action_in_public(exception) case exception.class when ActiveRecord::RecordNotFound, ActionController::UnknownAction render( :file => "#{RAILS_ROOT}/public/404.html", :status => "404 Not

I''m getting to the point now where I really need to start trapping the errors. So from my AWDWR book, I added the following directly from the book into application.rb... def rescue_action_in_public(exception) case exception when ActiveRecord::RecordNotFound, ActionController::UnknownAction render(:file => "#{RAILS_ROOT}/public/404.html",

I''m having trouble with rescue_action_in_public, both in getting it to work right in my rails app, and in writing tests to make sure. What I ultimately want to do is test for what a normal user would see when an error is trapped. I override local_request? like so: application.rb -------------- def rescue_action_in_public(exception) render :text => "oops" end def

Hi all! I''ve been using the excellent exception_nofitier ( http://agilewebdevelopment.com/plugins/exception_notifier ) a while now, but want to change the way it interacts with my application. I now have my own rescue_action_in_public which takes me to a "Error. Describe the problem"-page. After filling out some user data the user can then click on submit. This is where the

Hello, I''m new to rails and I''m trying to wrap my heads around how to spec controllers using RSpec (using rails 3rc1 and rspec 2.0.0.beta.19). The problem I''ve run into is when I want to test that my controllers respond with a 404 for unfound records. Whenever I run the spec, the ActiveRecord::RecordNotFound exception is not caught by rails, causing the spec

As I am in development environment, I wrote in my config/environment.rb ActionController::Base.consider_all_requests_local = false in my application.rb, I wrote def rescue_action_in_public(exception) case exception when RoutingError, UnknownAction render :file => "#{RAILS_ROOT}/public/404.html", :status => 404 else logger.error

In 2.3, exceptions raised by controllers under functional tests were by default propagated to the test, but by using rescue_action_in_public! a test could trigger the production, public behavior and then use assert_response or similar to test the expected result. This was implemented via coordination between ActionController::Rescue and ActionController::TestCase::RaiseActionExceptions. This

I copied (and modified) this code from AWDWR: def rescue_action_in_public(exception) case exception when ActiveRecord::RecordNotFound, ActionController::UnknownAction render :template=>''/error'', :layout=>''application'', :status=>''404 Not Found'' else render :template=>''/error'',

I''ve recently run into a problem with one of my applications that refuses to send emails using ActionMailer. Looking at the log, it become obvious what''s happening, the system is looking for templates with underscores at the end. Notice the exception_notification_ . For example: ActionView::ActionViewError (No rhtml, rxml, rjs or delegate template found for

In Rails 2.3.x, you can override render_optional_error_file like so: # ApplicationController.rb protected def render_optional_error_file(status_code) render :template => "errors/500", :status => 500, :layout => ''application'' end However, Rails 3 no longer has render_optional_error_file. Instead, you need to overriderescue_action_in_public, which I do:

hi, i''m trying to implement rescue_action_in_public as a catch-all to redirect to an error page when an exception is thrown (actually, just for testing, I''m rendering "ERROR"). However, putting def render_action_in_public render( :text=>"ERROR" ) end in either a specific controller or even application.rb, has no effect on the app redirecting on

Hi all, I''m trying to make for nicer system error handling, with the help of rescue_action_in_public (see Recipe 47, in ''Rails Recipes'') PROBLEM: While it lets me capture an incorrect db name in database.yml (for example), with lower level errors like when the DB server is just down, I still get the default system error screen for MySQL::ERROR :

I keep getting a blank page containing only the following: "There was a controller specfic error processing your request." Though I have the following in my application.rb def rescue_action_in_public(exception) case exception when UnknownAction, ActiveRecord::RecordNotFound then render :controller => "application", :action =>

The new rescue_from in edge rails seems to conflict with ActionWebService, which I need for various other purposes. When I define, for example (with AWS gem installed): <b>rescue_from ActionController::RoutingError, :with => :page_not_found</b> I get the exception: <b>uninitialized constant ActionWebService::Dispatcher::ActionController::Base</b> OK, so AWS

Greetings, I''m trying to catch all un-handled exceptions. I''m having problems handling the RoutingError and UnknownAction exceptions. I''ve added the following to my application controller as a protected method: def rescue_action(exception) render(:text => "error") end As far as I understand, this should catch all uncaught exceptions and override

With rspec 1.0.8 I have a spec in the directory: spec/units/controllers/application_controller_spec.rb require File.dirname(__FILE__) + ''/../../spec_helper'' class DummyController < ApplicationController def index raise "Prevent index from rendering" end end describe ApplicationController, "Handling errors in production", :behaviour_type =>

The specific error is: ActionController::RoutingError (no route found to match "/application/setservice" with {:method=>:post}) With actionpack-1.12.5 the default route handled /application/setservice. I have found a workaround by adding the route map.connect ''application/setservice'', :controller=>''application'',

OK ... so I''m not supposed to use it but ... Why doesn''t rescue_from ActionController::RoutingError work witht he code from http://www.rubyplus.org/episodes/20-Extended-RESTful-Authentication-Rails-2-App.html class ApplicationController < ActionController::Base helper :all # include all helpers, all the time # See ActionController::RequestForgeryProtection for details

I''m getting strange data back from my worker whenever I run our rails app with more than one dispatcher under lighttpd. just to give some info on what the app does: user submits data to rails app. rails app hands off data to worker, which goes and does it''s thing, storing results in an array of response objects (the array is an attribute of the worker). the response object