similar to: issue with rescue_action_in_public! and testing 404 responses

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 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''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

I have this in my application controller. def rescue_action_in_public(exception) logger.error("rescue_action_in_public executed") case exception when ActiveRecord::RecordNotFound, ::ActionController::UnknownAction, ::ActionController::RoutingError logger.warn("rendering 404 page") render(:file =>

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 =>

I''m trying to spec a dead simple "show non-existent record should render 404" case, but it seems the RecordNotFound exception is making it impossible for some reason. #controller def show @event = Event.find(params[:id]) end #spec - pretty much straight from the rspec site before do Event.stub!(:find) get :show, :id => ''broken'' end #

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

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",

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

Hi folks- I have the following map for default ''junk'' routes: map.connect ''*anything'', :controller => ''welcome'', :action => ''unknown'' Which works just fine for a URL like: "mysite.com/junkjunkjunk" However, it still tries to resolve an action when I do: "mysite.com/my_controller/junkjunkjunk"

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 :

Hi, I''m having a strange problem that only seems to be happening on our production server. I never get this error locally but get it quite often on the server. The other odd thing is it doesn''t seem to be resulting in any error pages on the site. Everything looks fine... I wanted to add a rescue_action_in_public to email me when there are errors. So I followed the

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

Hello! I was wondering, sometimes I raise an exception in my Rails apps, e.g.: raise SecurityError unless @post.user == logged_in_user Now: is there any way to catch that SecurityError exception somewhere and render a custom template? E.g., I want to render ''app/views/content/security_error.rhtml'' Does anyone know how to do this? Thanks a bunch, Rob

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

Hi, I''m using ActionController::rescue_action_in_public() to send emails when uncaught exceptions happen. Is it possible to write tests for that? Joe

Hey all, I am writing a plugin in which I want to stop the rendering of an action with an unauthorized response if the user is not authorized to view the resource. I am using a before filter to achieve this and inside that before filter I do it like so: render :text => "Unauthorized!", :status => :unauthorized, :layout => false The status is properly set since I see the

Hello, When I call an action with some invalid XML or JSON data a parse exception gets raised from within Rails/Ruby (REXML or ActiveSupport::JSON). The problem that I''ve got is how to handle these exceptions. In my application_controller.rb I have the following for debugging purposes: def rescue_action_in_public(exception) respond_to do |request| request.all { render :text =>