Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

better_errors is not working with Routing Error in Rails ? #220

Closed
wangyandongnx opened this issue Nov 28, 2013 · 2 comments
Closed

better_errors is not working with Routing Error in Rails ? #220

wangyandongnx opened this issue Nov 28, 2013 · 2 comments

Comments

@wangyandongnx
Copy link

It works great except that the default routing error page will be displayed instead of better_errors's page. Is this the right behavior?

——————————————————————————————————————
Ruby version 2.0.0 (x86_64-darwin12.5.0)
RubyGems version 2.1.11
Rack version 1.5
Rails version 4.0.1
JavaScript Runtime JavaScriptCore
Active Record version 4.0.1
Action Pack version 4.0.1
Action Mailer version 4.0.1
Active Support version 4.0.1
Middleware
Rack::Sendfile
ActionDispatch::Static
Rack::Lock

ActiveSupport::Cache::Strategy::LocalCache::Middleware:0x007fd08d0ec6e8

Rack::Runtime
Rack::MethodOverride
ActionDispatch::RequestId
Rails::Rack::Logger
ActionDispatch::ShowExceptions
ActionDispatch::DebugExceptions
BetterErrors::Middleware
ActionDispatch::RemoteIp
ActionDispatch::Reloader
ActionDispatch::Callbacks
ActiveRecord::Migration::CheckPending
ActiveRecord::ConnectionAdapters::ConnectionManagement
ActiveRecord::QueryCache
ActionDispatch::Cookies
ActionDispatch::Session::CookieStore
ActionDispatch::Flash
ActionDispatch::ParamsParser
Rack::Head
Rack::ConditionalGet
Rack::ETag
Application root /Users/wangyandong/Workspace/rails4/learning_rails
Environment development
Database adapter sqlite3
Database schema version 20131128045006
——————————————————————————————————————

@hdost
Copy link

hdost commented Dec 4, 2013

That's the whole point of it. If you are looking to only make it available in your development. Consider grouping it under development in your gem file.

@haileys
Copy link
Collaborator

haileys commented Apr 26, 2014

This seems like desired behaviour to me. AFAIK, routing errors like this in Rails are not 'true' errors, but rather a nicer 404 error page formatted like the Rails exception page. Please correct me if I'm wrong here.

In any case, the Rails routing error page seems more useful than Better Errors for this case, so I don't intend to fix or otherwise work around this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants