Since status_controller can consume lot of resources and it could be possible attack point for DoS, I am enabling it only for development mode.
in their :if block
…navigation rules will be adhered to in the UI
… results_count going to NaN in ui
…ave a current org
For development environment we have SQL logs in a different file: log/development.log - rails related logging log/development_sql.log - AR SQL I think it is very handsome thing and I am going to merge a small change that will do the same for test environment if there are no objections. log/test.log - rails related logging log/test_sql.log - AR SQL Please note those files, particularly ths SQL log, can grow in size very much. I recommend to create a symlink to /dev/null if you don't plan to use it, or delete it regularly (e.g. on the Hudson). In other words, after I merge this change, check out log/test.log when dealing with exceptions during unit testing. It's much more cleaner now and one can find backtraces faster.
Slightly improved debug logs