Mercurial > piecrust2
view garcon/messages/templates/error.html @ 1136:5f97b5b59dfe
bake: Optimize cache handling for the baking process.
- Get rid of the 2-level pipeline runs... handle a single set of passes.
- Go back to load/render segments/layout passes for pages.
- Add descriptions of what each job batch does.
- Improve the taxonomy pipeline so it doesn't re-bake terms that don't need
to be re-baked.
- Simplify some of the code.
author | Ludovic Chabant <ludovic@chabant.com> |
---|---|
date | Mon, 23 Apr 2018 21:47:49 -0700 |
parents | 79aefe82c6b6 |
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 %}