[Rails] Re: Problem setting log level

2012-10-17 Thread Daniel Sundqvist
Christian: Hey, that was actually the problem! :) I was having a blank in the path of my project directory, and removing that fixed the problem. Great, this was beginning to get somewhat frustrating... I'm am running Debian Wheezy with rvm and Ruby 1.9.3-p286 so the setup is pretty similar. T

[Rails] Re: Problem setting log level

2012-10-16 Thread Christian G.
It seems (at least on ubuntu), that umlauts or blanks in the path of the rails app, will cause rails to show the "We're sorry,..." screen without any backtrace. By removing the umlauts and blanks the right backtrace is showing up. Hope this helps. Christian -- Posted via http://www.ruby-foru

[Rails] Re: Problem setting log level

2012-10-16 Thread Christian G.
Hi Daniel, i'm facing the same problem and i'm using ubuntu 12.04, rvm, ruby 1.9.2-p320. Do you have a similar setup and os? Christian -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post t

[Rails] Re: Problem setting log level

2012-09-24 Thread Daniel Sundqvist
Yes it is set to true. It seems like this is the default behavior on my rails installation. I did a test: i created a new rails project, generated a scaffold model, inserted a faulty link_to helper like: <%= link_to 'bogus', some_bogus_non_existing_path %> in one of the views. I start the developme

[Rails] Re: Problem setting log level

2012-09-24 Thread Daniel Sundqvist
walterdavis: "We're sorry, but something went wrong" is the error message i get. When i start the development server i see "Rails 3.2.8 application starting in development on http://0.0.0.0:3000";. log/development.log is the logfile that is used. Seems to me that i'm in development mode. I hav

[Rails] Re: Problem setting log level

2012-09-23 Thread Daniel Sundqvist
Update: Seems like the right log level is set. But for som reason i dont see an error message and a stacktrace when encountering an error. Is there more configuration to be done or should this be enough to be able to see the stacktrace? -- Posted via http://www.ruby-forum.com/. -- You received

[Rails] Re: Problem setting log level

2012-09-23 Thread Daniel Sundqvist
Btw I am using Rails 3.2.3. I have checked that Rails.logger.level = 0 so it should be :debug. And i'm also sure that i'm running in development mode. But still I just get this one line telling me about an internal error wich doesnt help me a bit. -- Posted via http://www.ruby-forum.com/. --