Mercurial > piecrust2
view build/messages/templates/error.html @ 231:137bcd498ef9
serve: Fix a bug where empty route metadata is not the same as invalid route.
Some routes can capture no metadata at all, like for example when
`foo/%path:slug%` is capturing URL `foo`. The route is still valid, so it
returns an empty dictionary. It's not the same as returning `None`, which means
"no match".
author | Ludovic Chabant <ludovic@chabant.com> |
---|---|
date | Wed, 11 Feb 2015 08:31:13 -0800 |
parents | a951cd4ef361 |
children |
line wrap: on
line source
{% extends "default.html" %} {% block content %} {{content|safe}} {# The following is `raw` because we want it to be in the produced page, so it can then be templated on the fly with the error messages #} {% raw %} {% if details %} <div class="error-details"> <p>Error details:</p> <ul> {% for desc in details %} <li>{{ desc }}</li> {% endfor %} </ul> </div> {% endif %} {% endraw %} {% endblock %} {% block footer %} {% pcformat 'textile' %} p(note). You're seeing this because something wrong happend. To see detailed errors with callstacks, run chef with the @--debug@ parameter, append @?!debug@ to the URL, or initialize the @PieCrust@ object with @{'debug': true}@. On the other hand, to see you custom error pages, set the @site/display_errors@ setting to @false@. {% endpcformat %} {% endblock %}