Mercurial > piecrust2

view piecrust/resources/messages/error.html @ 334:b034f6f15e22

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
bake: Several bug taxonomy-related fixes for incorrect incremental bakes. * Improve how the baker processes taxonomy terms and figures out what needs to be re-baked or not. * Create bake entries for clean taxnomy terms so they're not deleted by an incremental bake. * Add more information to bake records. * Slugify taxonomy terms is now done by the route in one place. * Fix a bug where the cache key for invalidating rendered segments was not computed the same way as when the caching was done. * Fix how term combinations are passed around, rendered, printed, parsed, etc. (TODO: more word needed in the routing functions) * Expose to the template whether a taxonomy term is a combination or not. * Display term combinations better in the built-in theme. * Rename `route.taxonomy` to `route.taxonomy_name` to prevent confusion. * Add options to show bake records for previous bakes.
author Ludovic Chabant <ludovic@chabant.com>
date Fri, 03 Apr 2015 10:59:50 -0700
parents a951cd4ef361
children
line wrap: on
line source

<!doctype html>
<html>
<head>
    <title>The Cake Just Burned!</title>
    <meta name="generator" content="PieCrust" />
	<link rel="stylesheet" type="text/css" href="http://fonts.googleapis.com/css?family=Lobster">
	<style>
		body {
			margin: 0;
			padding: 1em;
			background: #eee;
			color: #000;
			font-family: Georgia, serif;
		}
		h1 {
			font-size: 4.5em;
			font-family: Lobster, 'Trebuchet MS', Verdana, sans-serif;
			text-align: center;
			font-weight: bold;
            margin-top: 0;
			color: #333;
			text-shadow: 0px 2px 5px rgba(0,0,0,0.3);
		}
		h2 {
			font-size: 2.5em;
            font-family: 'Lobster', 'Trebuchet MS', Verdana, sans-serif;
		}
		code {
			background: #ddd;
			padding: 0 0.2em;
		}
        #preamble {
            font-size: 1.2em;
            font-style: italic;
            text-align: center;
            margin-bottom: 0;
        }
		#container {
			margin: 0 20%;
		}
        #content {
            margin: 2em 1em;
        }
        .error-details {
            color: #d11;
        }
		.note {
			margin: 3em;
			color: #888;
			font-style: italic;
		}
	</style>
</head>
<body>
    <div id="container">
        <div id="header">
            <p id="preamble">A Message From The Kitchen:</p>
			<h1>The Cake Just Burned!</h1>
		</div>
        <hr />
        <div id="content">
            


{% if details %}
<div class="error-details">
    <p>Error details:</p>
    <ul>
    {% for desc in details %}
        <li>{{ desc }}</li>
    {% endfor %}
    </ul>
</div>
{% endif %}
		</div>
        <hr />
        	<p class="note">You&#8217;re seeing this because something wrong happend. To see detailed errors with callstacks, run chef with the <code>--debug</code> parameter, append <code>?!debug</code> to the <span class="caps">URL</span>, or initialize the <code>PieCrust</code> object with <code>{'debug': true}</code>. On the other hand, to see you custom error pages, set the <code>site/display_errors</code> setting  to <code>false</code>.</p>	</div>
</body>
</html>