similar to: Missing action error not being caught

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

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

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

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

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 am trying to develop a new webapp using Rails 1.2.1. I am installing it onto a production web server running Apache w/ fastcgi. The server already has some older webapps running on it using an older version of Rails. The apps are not installed in the document root; they each have their own subdirectory which is a symlink for the apache document root to the "public" directory of each

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 my application.rb''s rescue_action_in_public, why do I need to prefix ActionController::UnknownAction with ::, when ActiveRecord::RecordNotFound (no :: prefix) works? If I don''t prefix the former, I get an unknown constant (or similar) error. Joe -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message

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

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

I am trying to locate the following in the current 1.0 source tree: ActiveRecord::RecordNotFound ActionController::UnknownAction Looking at the API docs, I''ve been unable to track these down. Can someone help?

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''m new in ruby on rails. i created a controller which has 2 views index, add_to_cart & inside index i created "button_to" which references to add_to_cart view, but when i click on this button UnKnownAction exception appear to me, i don''t know why this happen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are

hi , in my logs i see that: Completed in 1480ms (View: 267, DB: 90) | 200 OK [http://192.168.2.9/xyz/99] SQL (1.4ms) SET NAMES ''utf8'' SQL (0.7ms) SET SQL_AUTO_IS_NULL=0 Processing xyzsController#images to gif (for 192.168.2.3 at 2010-10-28 15:22:35) [GET] Parameters: {"id"=>"loading"} ActionController::UnknownAction (No action responded to

Hello All, I''ve developed RoR on windowsXP have deployed that on Linux. Everythings works fine when working on windows. Things are fine on Linux too untill I try to create new entry. I tried but couldn''t find any relevent information why it should happen only to this "specific" create action. I''m saying this because different create on other forms are

Please forgive me if this is a stupid question. If it has been answered already, please point me to the answer, as my searching has been fruitless. How can I programatically handle 404s and 500s when using Mongrel? I''ve read about using a proxy server config (.htaccess for example) to render an ErrorDocument rather than whatever comes from Rails, but I need something different. I would

I create a simple engine with a simple controller: class FredController < ApplicationController def hello render :text => ''Hello, world!'' end end and I create a simple functional test within the engine: class FredControllerTest < Test::Unit::TestCase ... def test_hello get :hello assert_response :success end

Hi Folks, I''m having trouble with setting up web services with layered dispatching. I''ve defined my controller (backend_controller.rb) as: class BackendController < ApplicationController web_service_dispatching_mode :layered web_service_scaffold :invoke web_service (:car) {CarService.new} end and my service (node_service.rb) as: