Geek Answers Handbook

Rails 3.2 development mode does not display a full page with a backtrace error, etc.

I just upgraded to the rails. 3.2 Everything works fine, except for the error pages, the usual information about development debugging is no longer displayed. Instead, it shows a standard production error page (white background with red text in the middle:

"We're sorry, but something went wrong. We have been notified of this issue and we will look at it soon."

Is there a new parameter or something that I am missing for 3.2 rails? I have read the update instructions and cannot see the mention anywhere. I tried downgrading to 3.1.3 and the error pages work again, so this is definitely a problem with rails 3.2. Thanks.

+6
ruby-on-rails ruby-on-rails-3
source share
3 answers

Check config.consider_all_requests_local inside development.rb . It must be set to true in order to display full error reports.

+9
source share

Nicolas , I ran into the same problem and only saw the message We're sorry, but something went wrong. and nothing in the magazines.

The problem was in UTF-8 characters , so adding an encoding declaration to the beginning of the file resolved it:

 # encoding = utf-8
+4
source share

If neither the jibiels nor Dmitrys solution helped, try the solution mentioned here: Rails does not log tempalte errors in development mode

(Maybe this will also help you, @Nicolas)

0
source share

More articles:


All Articles