<h1>Routing Error</h1>
<p><pre><%=h @exception.message %></pre></p>
<% unless @exception.failures.empty? %>
  <p>
    <h2>Failure reasons:</h2>
    <ol>
    <% @exception.failures.each do |route, reason| %>
      <li><code><%=h route.inspect.gsub('\\', '') %></code> failed because <%=h reason.downcase %></li>
    <% end %>
    </ol>
  </p>
<% end %>
<p>
  Try running <code>rake routes</code> for more information on available routes.
</p>
<h1>Routing Error</h1>
<p><pre><%=h @exception.message %></pre></p>
<% unless @exception.failures.empty? %>
  <p>
    <h2>Failure reasons:</h2>
    <ol>
    <% @exception.failures.each do |route, reason| %>
      <li><code><%=h route.inspect.gsub('\\', '') %></code> failed because <%=h reason.downcase %></li>
    <% end %>
    </ol>
  </p>
<% end %>
<p>
  Try running <code>rake routes</code> for more information on available routes.
</p>

<%= render :template => "rescues/_trace" %>

Add backtrace to development routing error page
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.
