view build/messages/templates/error.html @ 371:c2ca72fb7f0b 2.0.0a8

caching: Use separate caches for config variants and other contexts. * The `_cache` directory is now organized in multiple "sub-caches" for different contexts. * A new context is created when config variants or overrides are applied. * `serve` context uses a different context that the other commends, to prevent the `bake` command's output from messing up the preview server (e.g. with how asset URLs are generated differently between the two). * Fix a few places where the cache directory was referenced directly.
author Ludovic Chabant <ludovic@chabant.com>
date Sun, 03 May 2015 23:59:46 -0700
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 %}