I must be missing something or have something misconfigured, but I get no stack-trace when there is an error in the code behind a view.
If the view doesn't compile, then I see an error & stacktrace, but all other errors I get a "lost network connection" from the browser, and nothing at all in the server output or development.log.
It's been that way with this app I'm working on for as long as I can remember. Sometimes I wrap the whole view in a begin/rescue block to find out what's going on, but now the annoyance level has reached the point where I'm posting about it
I have no idea why this happens, or what I could have done to make it start happening, or even where to start to figure out what's going on with it.
I must be missing something or have something misconfigured, but I get no stack-trace when there is an error in the code behind a view.
If the view doesn't compile, then I see an error & stacktrace, but all other errors I get a "lost network connection" from the browser, and nothing at all in the server output or development.log.
It's been that way with this app I'm working on for as long as I can remember. Sometimes I wrap the whole view in a begin/rescue block to find out what's going on, but now the annoyance level has reached the point where I'm posting about it
I have no idea why this happens, or what I could have done to make it start happening, or even where to start to figure out what's going on with it.
Anyone else have/fix/understand this problem?
Are these nil errors or something else? There's a setting in your config/environments/ files called "config.whiny_nils". If you've set that to false it won't log nil errors.
I had this exact same problem and I only managed to find information
that suggested that this so-called White Screen of Death (WSOD) was
due to problems with sessions. As I had recently moved to using
SQLSessionStore, I thought this was to blame but in fact it was a mere
coincidence and my problem was with using views named in the latest
Edge Rails format of action.format.erb (e.g. show.html.erb). Once I
switched to using action.erb, everything was fine again.
You mentioned that you've had this problem for a while however and I
believe the naming scheme I mention is recent so I doubt it is to
blame, however I thought it was worth mentioning.
The only other advice I've seen is to run `rake db:sessions:clear` (if
you are using database sessions) or `rake tmp:sessions:clear` if you
are using the default file-system-based sessions.
I'll experiment with some this and see what happens. Did you see my
reply where I mentioned that I discovered that the problem was
related to Globalize? Maybe globalize is doing something that
triggers one of these issues.
