schneems e737f142bd Add backtrace to development routing error page ... If a user gets a routing error due to a view helper such as using user_path without an :id they must go to their logs to see the backtrace. By adding in the trace template, a user can see which line the error occurred on without leaving the browser. When a routing error occurs outside of the view the application trace will be blank and will not confuse developers.		2012-05-02 16:01:08 -07:00
..
_request_and_response.erb	Only show dump of regular env methods on exception screen (not all the rack crap) [DHH]	2011-05-04 19:56:56 -05:00
_trace.erb	Remove remaining warnings on _trace by adding parenthesis to gsub arguments.	2010-09-28 16:12:07 -03:00
diagnostics.erb	Don't pluralize, camelize.	2011-05-06 17:00:59 +02:00
layout.erb	CSS fix to prevent error output from being breaking out of body element.	2011-11-03 10:01:32 -04:00
missing_template.erb	Extract ActionController rescue templates into Rescue and ShowExceptions middleware.	2009-05-02 23:02:22 -05:00
routing_error.erb	Add backtrace to development routing error page	2012-05-02 16:01:08 -07:00
template_error.erb	render :template is faster than render :file	2011-01-01 13:44:34 -02:00
unknown_action.erb	Extract ActionController rescue templates into Rescue and ShowExceptions middleware.	2009-05-02 23:02:22 -05:00