Ghost/core/server/views/error.hbs

{{!< default}}
<section class="error-content error-404 js-error-container">
    <section class="error-details">
        <figure class="error-image">
            <img class="error-ghost" src="/ghost/img/404-ghost@2x.png" srcset="/ghost/img/404-ghost.png 1x, /ghost/img/404-ghost@2x.png 2x"/>
        </figure>
        <section class="error-message">
            <h1 class="error-code">{{code}}</h1>
            <h2 class="error-description">{{message}}</h2>
        </section>
    </section>
</section>
{{#if stack}}
    <section class="error-stack">
        <h3>Stack Trace</h3>
        <p><strong>{{message}}</strong></p>
        <ul class="error-stack-list">
            {{#foreach stack}}
                <li>
                    at
                    {{#if function}}<em class="error-stack-function">{{function}}</em>{{/if}}
                    <span class="error-stack-file">({{at}})</span>
                </li>
            {{/foreach}}
        </ul>
    </section>
{{/if}}
Initial 404 Error Handling Support Fixes #356 - Adds new generic methods for handling errors to errorHandling.js - Initialises generic methods as middleware - Created error.hbs view in admin - Error handler searches for error.hbs view file in user theme folder and renders it if available, otherwise lets the error fall through to express. - We could change the final behaviour to render a default ghost template should the user template be missing - Because it currently isn't possible to require(ghost) in errorHandling.js, it was necessary to duplicate some aspects of the ghost path init code inside errorhandling.js. This should be cleaned up and moved back into ghost.js when possible. 2013-09-17 14:56:05 +04:00			`{{!< default}}`
			`<section class="error-content error-404 js-error-container">`
404 Page vertical centering closes #791 2013-09-18 06:07:22 +04:00			`<section class="error-details">`
			`<figure class="error-image">`
500 Series Error Handling & Stack Traces Fixes #825 - Changes the way the error middleware is delivered in server.js, moving all the logic back into errorHandling.js - Alters error logging to use console.error (probably more appropriate) instead of console.log - Changes error tests to accomodate for these alterations - Alters user-error and error hbs templates to incorporate stack traces - Adds additional styling for error pages to accomodate stack traces - Added logic to parse and deliver formatted stack traces Notes: ====== - Jslint gets in the way of the regex I've got to use to parse the stack. (It cites 'security reasons' which are not relevant in this case.) I needed to add a condition to relax it at the top of errorHandling.js - The stack trace should probably be added as a partial, but I figured it was out of scope for this PR. 2013-09-19 06:50:06 +04:00			`<img class="error-ghost" src="/ghost/img/404-ghost@2x.png" srcset="/ghost/img/404-ghost.png 1x, /ghost/img/404-ghost@2x.png 2x"/>`
404 Page vertical centering closes #791 2013-09-18 06:07:22 +04:00			`</figure>`
			`<section class="error-message">`
500 Series Error Handling & Stack Traces Fixes #825 - Changes the way the error middleware is delivered in server.js, moving all the logic back into errorHandling.js - Alters error logging to use console.error (probably more appropriate) instead of console.log - Changes error tests to accomodate for these alterations - Alters user-error and error hbs templates to incorporate stack traces - Adds additional styling for error pages to accomodate stack traces - Added logic to parse and deliver formatted stack traces Notes: ====== - Jslint gets in the way of the regex I've got to use to parse the stack. (It cites 'security reasons' which are not relevant in this case.) I needed to add a condition to relax it at the top of errorHandling.js - The stack trace should probably be added as a partial, but I figured it was out of scope for this PR. 2013-09-19 06:50:06 +04:00			`<h1 class="error-code">{{code}}</h1>`
			`<h2 class="error-description">{{message}}</h2>`
404 Page vertical centering closes #791 2013-09-18 06:07:22 +04:00			`</section>`
			`</section>`
500 Series Error Handling & Stack Traces Fixes #825 - Changes the way the error middleware is delivered in server.js, moving all the logic back into errorHandling.js - Alters error logging to use console.error (probably more appropriate) instead of console.log - Changes error tests to accomodate for these alterations - Alters user-error and error hbs templates to incorporate stack traces - Adds additional styling for error pages to accomodate stack traces - Added logic to parse and deliver formatted stack traces Notes: ====== - Jslint gets in the way of the regex I've got to use to parse the stack. (It cites 'security reasons' which are not relevant in this case.) I needed to add a condition to relax it at the top of errorHandling.js - The stack trace should probably be added as a partial, but I figured it was out of scope for this PR. 2013-09-19 06:50:06 +04:00			`</section>`
			`{{#if stack}}`
			`<section class="error-stack">`
			`<h3>Stack Trace</h3>`
			`<p><strong>{{message}}</strong></p>`
			`<ul class="error-stack-list">`
			`{{#foreach stack}}`
			`<li>`
			`at`
			`{{#if function}}<em class="error-stack-function">{{function}}</em>{{/if}}`
			`<span class="error-stack-file">({{at}})</span>`
			`</li>`
			`{{/foreach}}`
			`</ul>`
			`</section>`
			`{{/if}}`