view build/messages/templates/error.html @ 380:f33712c4cfab

routing: Fix bugs with matching URLs with correct route but missing metadata. When matching a route like `/foo/%slug%` against an URL like `/foo`, the route will (correctly) return a match, but it will be completely missing the `slug` metadata, resulting in problems elsewhere. This change makes it so that any missing route metadata will be filled in with an empty string. And because this means generated URLs may differ from the incoming URL when using trailing slashes (`/foo/` _vs._ `/foo`), we make the assert in the chef server handle those discrepancies.
author Ludovic Chabant <ludovic@chabant.com>
date Sun, 10 May 2015 00:34:21 -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 %}