You are not logged in. Please login or register.
Rails Forum - Ruby on Rails Help and Discussion Forum » Setup and Configuration » Rails 2.2, no stack trace
I've installed Rails 2.2 for a new app I've decided to start, and when I have an error in development mode it just shows me a generic 500 error rather than a stack trace. Has anyone else seen this and if so how did you change it back to having a stack trace? I have a standard rails install with no config changed with the rails gems frozen into vendor.
Cheers.
Are you running on Mongrel or a standard HTTP server like Apache/Lighthttpd?
Mongrel.
The stack trace shows in my terminal where the script/server is running, but that's annoying.
I have the same problem. Exeptions are only shown in the console and not in the browser anymore.
Has anyone solved this, yet? I'm running in mongrel/webrick in development mode with the following standard settings in "config/environments/development.rb":
config.cache_classes = false
config.whiny_nils = true
config.action_controller.consider_all_requests_local = true
config.action_view.debug_rjs = true
config.action_controller.perform_caching = false
config.action_mailer.raise_delivery_errors = false
I tracked it down to rspec. I'm using the rspec and rspec-rails gem plugins and require them in "config/environment.rb". When I remove the following lines...
config.gem 'rspec-rails', :lib => 'spec/rails'
config.gem 'rspec', :lib => 'spec'
... I get back my lovely stacktrace in the browser...
Ah, thank you! I was having this problem as well. You don't realize how much you'll miss the stacktraces until they're gone :).
It seems to specifically be the 'rspec-rails' line, at least on my system. I would like to have this listed as a gem dependency, if possible. Anyone have any ideas as to how to keep the line without loosing the traces?
Last edited by cwalcott (2008-12-10 20:32:36)
Awesome, thank you.
