TryGhost/Ghost
1
0
Fork 0
mirror of https://github.com/TryGhost/Ghost.git synced 2024-11-29 15:12:58 +03:00
Code Issues Projects Releases Wiki Activity
e8248cdc9e
Ghost/core/server/views/error.hbs

59 lines
2.3 KiB
Handlebars
Raw Normal View History

Default 404/500 Error Message Fixes #792 - Added default template for errors where a user has not defined a custom template (error.hbs) in the theme folder - Now searches for user-error.hbs in the server view folder should a user template not be present.
2013-09-18 09:12:53 +04:00
<!doctype html>
<!--[if (IE 8)&!(IEMobile)]><html class="no-js lt-ie9" lang="en"><![endif]-->
<!--[if (gte IE 9)| IEMobile |!(IE)]><!--><html class="no-js" lang="en"><!--<![endif]-->
Replace SASS with assets from Ghost-UI closes #2368 - Remove Ruby dependency (Gemfiles) - Remove sass/fonts from core/client/assets/ - Add copy task to Gruntfile to copy over ghost-ui assets - Install Ghost-UI via bower - Changed .npmignore/.gitignore - Remove grunt-contrib-sass dependency - Remove mentions of Ruby in CONTRIBUTING.md
2014-03-08 22:43:52 +04:00
<head>
<meta http-equiv="Content-Type" content="text/html" charset="UTF-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
Default 404/500 Error Message Fixes #792 - Added default template for errors where a user has not defined a custom template (error.hbs) in the theme folder - Now searches for user-error.hbs in the server view folder should a user template not be present.
2013-09-18 09:12:53 +04:00
Fixed error trying to render 404 for missing asset refs #8868 - Loading the admin prior to a build results in: Failed to lookup view "error-404" in views directory - This fixes that error, by splitting the HTMLErrorRenderer and the ThemeErrorRenderer into two separate things
2017-12-22 22:44:09 +03:00
<title>{{statusCode}} — {{message}}</title>
Theming updates for password protection refs #4993, #5073 - Removed nonexistent helpers siteDescription and bodyClass from admin templates - Changed password.hbs to private.hbs to match the route name - added a new input_password helper for rendering the password input with the correct properties - removed the forward input as this can be handled via urls only - moved 'private' to routeKeywords - added 'private' context - minor update to text next to the password in settings
2015-05-13 12:26:49 +03:00
Replace SASS with assets from Ghost-UI closes #2368 - Remove Ruby dependency (Gemfiles) - Remove sass/fonts from core/client/assets/ - Add copy task to Gruntfile to copy over ghost-ui assets - Install Ghost-UI via bower - Changed .npmignore/.gitignore - Remove grunt-contrib-sass dependency - Remove mentions of Ruby in CONTRIBUTING.md
2014-03-08 22:43:52 +04:00
<meta name="HandheldFriendly" content="True">
<meta name="MobileOptimized" content="320">
<meta name="viewport" content="user-scalable=no, width=device-width, initial-scale=1, maximum-scale=1">
<meta name="apple-mobile-web-app-capable" content="yes" />
Default 404/500 Error Message Fixes #792 - Added default template for errors where a user has not defined a custom template (error.hbs) in the theme folder - Now searches for user-error.hbs in the server view folder should a user template not be present.
2013-09-18 09:12:53 +04:00
Replace SASS with assets from Ghost-UI closes #2368 - Remove Ruby dependency (Gemfiles) - Remove sass/fonts from core/client/assets/ - Add copy task to Gruntfile to copy over ghost-ui assets - Install Ghost-UI via bower - Changed .npmignore/.gitignore - Remove grunt-contrib-sass dependency - Remove mentions of Ruby in CONTRIBUTING.md
2014-03-08 22:43:52 +04:00
<meta http-equiv="cleartype" content="on">
Default 404/500 Error Message Fixes #792 - Added default template for errors where a user has not defined a custom template (error.hbs) in the theme folder - Now searches for user-error.hbs in the server view folder should a user template not be present.
2013-09-18 09:12:53 +04:00
Asset amends (#8294) refs #8221 🔥 Remove ghost=true concept from asset url helper ✨ 💯 Introduce CSS minification with cssnano - add new grunt-cssnano dependency - wire up grunt task to minify public/ghost.css 🎨 Rename minification config & hash params - Change minifyInProduction -> hasMinFile - this means this asset should have a .min file available - Change minifyAssets -> useMinFiles - this means that in this env we want to serve .min files if available 🎨 Update public/ghost.css to serve .min for prod - add the new `hasMinFile` property 🎨 Move minified asset handling to asset_url util - this logic should be in the util, not the asset helper - updated tests 📖 Error handler always needs asset helper - this removes the TODO and adds a more sensible comment - we also need to update our theme documentation around error templates 🔥 Don't use asset helper in ghost head - use getAssetUrl util instead! - removed TODO 📖 Update proxy docs 🎨 Simplify asset helper & add tests - this refactor is a step prior to moving this from metadata to being a url util - needed to skip some new tests 🐛 Add missing handler for css file
2017-04-10 12:30:21 +03:00
<link rel="stylesheet" href="{{asset "public/ghost.css" hasMinFile="true"}}"/>
Split css server templates (#8234) closes #8126 * Remove default template dependency on client side CSS See Issue #8126 Adds these files under /shared - normalizer.css - error.css - extracted.css (for subscribers.css and private.css) Also makes these files available as public static content * Remove default template dependency on client CSS closes #8126 needs e3acd3c This is a replacement PR of #8217 (thanks @TienSFU25 for the whole work 🤗), because these changes are needed urgently and blocking other work. Adds a new `ghost.css` file in `/core/shared/` to be used for server side template rendering (`error.hbs`, `subscribe.hbs` and `private.hbs`).
2017-04-04 12:06:38 +03:00
Replace SASS with assets from Ghost-UI closes #2368 - Remove Ruby dependency (Gemfiles) - Remove sass/fonts from core/client/assets/ - Add copy task to Gruntfile to copy over ghost-ui assets - Install Ghost-UI via bower - Changed .npmignore/.gitignore - Remove grunt-contrib-sass dependency - Remove mentions of Ruby in CONTRIBUTING.md
2014-03-08 22:43:52 +04:00
</head>
Theming updates for password protection refs #4993, #5073 - Removed nonexistent helpers siteDescription and bodyClass from admin templates - Changed password.hbs to private.hbs to match the route name - added a new input_password helper for rendering the password input with the correct properties - removed the forward input as this can be handled via urls only - moved 'private' to routeKeywords - added 'private' context - minor update to text next to the password in settings
2015-05-13 12:26:49 +03:00
<body>
Replace SASS with assets from Ghost-UI closes #2368 - Remove Ruby dependency (Gemfiles) - Remove sass/fonts from core/client/assets/ - Add copy task to Gruntfile to copy over ghost-ui assets - Install Ghost-UI via bower - Changed .npmignore/.gitignore - Remove grunt-contrib-sass dependency - Remove mentions of Ruby in CONTRIBUTING.md
2014-03-08 22:43:52 +04:00
<main role="main" id="main">
Fixup broken error page styles
2015-06-08 13:13:42 +03:00
<div class="gh-app">
<div class="gh-viewport">
<div class="gh-view">
<section class="error-content error-404 js-error-container">
<section class="error-details">
<section class="error-message">
Fixed error trying to render 404 for missing asset refs #8868 - Loading the admin prior to a build results in: Failed to lookup view "error-404" in views directory - This fixes that error, by splitting the HTMLErrorRenderer and the ThemeErrorRenderer into two separate things
2017-12-22 22:44:09 +03:00
<h1 class="error-code">{{statusCode}}</h1>
Fixup broken error page styles
2015-06-08 13:13:42 +03:00
<h2 class="error-description">{{message}}</h2>
✨ Aliased {{@blog}} as {{@site}} in the theme API - we're going to remove @blog in Ghost 3.0 in favour of @site - @site is the theme-layer equivalent of the Content API settings endpoint
2019-01-03 20:52:37 +03:00
<a class="error-link" href="{{@site.url}}">Go to the front page →</a>
Fixup broken error page styles
2015-06-08 13:13:42 +03:00
</section>
</section>
</section>
🎨 gscan 1.1.0 & optimisations refs #8222 - differentiate between errors and fatal errors - use gscan errors in theme middleware - Adds a new `error()` method to `currentActiveTheme` constructor which will return the errors we receive from gscan - In middleware, if a theme couldn't be activated because it's invalid, we'll fetch the erros and send them to our error handler. We also use a new property `hideStack` to control, if the stack (in dev mode and if available) should be shown or the gscan errors (in prod mode, or in dev if no stack error) - In our error handler we use this conditional to send a new property `gscan` to our error theme - In `error.hbs` we'll iterate through possible `gscan` error objects and render them. - remove stack printing - stack for theme developers in development mode doesn't make sense - stack in production doesn't make sense - the stack is usually hard to read - if you are developer you can read the error stack on the server log - utils.packages: transform native error into Ghost error - use `onlyFatalErrors` for gscan format and differeniate fatal errors vo.2 - optimise bootstrap error handling - transform theme is missing into an error - add new translation key - show html tags for error.hbs template: rule
2017-05-31 19:42:42 +03:00
{{#if errorDetails}}
<section class="error-stack">
<h3>Theme errors</h3>
<ul class="error-stack-list">
Update each to foreach loop
2019-07-12 12:08:45 +03:00
{{#foreach errorDetails}}
🎨 gscan 1.1.0 & optimisations refs #8222 - differentiate between errors and fatal errors - use gscan errors in theme middleware - Adds a new `error()` method to `currentActiveTheme` constructor which will return the errors we receive from gscan - In middleware, if a theme couldn't be activated because it's invalid, we'll fetch the erros and send them to our error handler. We also use a new property `hideStack` to control, if the stack (in dev mode and if available) should be shown or the gscan errors (in prod mode, or in dev if no stack error) - In our error handler we use this conditional to send a new property `gscan` to our error theme - In `error.hbs` we'll iterate through possible `gscan` error objects and render them. - remove stack printing - stack for theme developers in development mode doesn't make sense - stack in production doesn't make sense - the stack is usually hard to read - if you are developer you can read the error stack on the server log - utils.packages: transform native error into Ghost error - use `onlyFatalErrors` for gscan format and differeniate fatal errors vo.2 - optimise bootstrap error handling - transform theme is missing into an error - add new translation key - show html tags for error.hbs template: rule
2017-05-31 19:42:42 +03:00
<li>
<em class="error-stack-function">{{{rule}}}</em>
Update each to foreach loop
2019-07-12 12:08:45 +03:00
{{#foreach failures}}
🎨 gscan 1.1.0 & optimisations refs #8222 - differentiate between errors and fatal errors - use gscan errors in theme middleware - Adds a new `error()` method to `currentActiveTheme` constructor which will return the errors we receive from gscan - In middleware, if a theme couldn't be activated because it's invalid, we'll fetch the erros and send them to our error handler. We also use a new property `hideStack` to control, if the stack (in dev mode and if available) should be shown or the gscan errors (in prod mode, or in dev if no stack error) - In our error handler we use this conditional to send a new property `gscan` to our error theme - In `error.hbs` we'll iterate through possible `gscan` error objects and render them. - remove stack printing - stack for theme developers in development mode doesn't make sense - stack in production doesn't make sense - the stack is usually hard to read - if you are developer you can read the error stack on the server log - utils.packages: transform native error into Ghost error - use `onlyFatalErrors` for gscan format and differeniate fatal errors vo.2 - optimise bootstrap error handling - transform theme is missing into an error - add new translation key - show html tags for error.hbs template: rule
2017-05-31 19:42:42 +03:00
<p><span class="error-stack-file">Ref: {{ref}}</span></p>
<p><span class="error-stack-file">Message: {{message}}</span></p>
Update each to foreach loop
2019-07-12 12:08:45 +03:00
{{/foreach}}
🎨 gscan 1.1.0 & optimisations refs #8222 - differentiate between errors and fatal errors - use gscan errors in theme middleware - Adds a new `error()` method to `currentActiveTheme` constructor which will return the errors we receive from gscan - In middleware, if a theme couldn't be activated because it's invalid, we'll fetch the erros and send them to our error handler. We also use a new property `hideStack` to control, if the stack (in dev mode and if available) should be shown or the gscan errors (in prod mode, or in dev if no stack error) - In our error handler we use this conditional to send a new property `gscan` to our error theme - In `error.hbs` we'll iterate through possible `gscan` error objects and render them. - remove stack printing - stack for theme developers in development mode doesn't make sense - stack in production doesn't make sense - the stack is usually hard to read - if you are developer you can read the error stack on the server log - utils.packages: transform native error into Ghost error - use `onlyFatalErrors` for gscan format and differeniate fatal errors vo.2 - optimise bootstrap error handling - transform theme is missing into an error - add new translation key - show html tags for error.hbs template: rule
2017-05-31 19:42:42 +03:00
</li>
Update each to foreach loop
2019-07-12 12:08:45 +03:00
{{/foreach}}
🎨 gscan 1.1.0 & optimisations refs #8222 - differentiate between errors and fatal errors - use gscan errors in theme middleware - Adds a new `error()` method to `currentActiveTheme` constructor which will return the errors we receive from gscan - In middleware, if a theme couldn't be activated because it's invalid, we'll fetch the erros and send them to our error handler. We also use a new property `hideStack` to control, if the stack (in dev mode and if available) should be shown or the gscan errors (in prod mode, or in dev if no stack error) - In our error handler we use this conditional to send a new property `gscan` to our error theme - In `error.hbs` we'll iterate through possible `gscan` error objects and render them. - remove stack printing - stack for theme developers in development mode doesn't make sense - stack in production doesn't make sense - the stack is usually hard to read - if you are developer you can read the error stack on the server log - utils.packages: transform native error into Ghost error - use `onlyFatalErrors` for gscan format and differeniate fatal errors vo.2 - optimise bootstrap error handling - transform theme is missing into an error - add new translation key - show html tags for error.hbs template: rule
2017-05-31 19:42:42 +03:00
</ul>
</section>
Fixup broken error page styles
2015-06-08 13:13:42 +03:00
{{/if}}
</div>
</div>
Center default user-error (404, etc.) See #3810 - Only thing missing: <div id=“container”></div>. Added.
2014-08-19 00:45:03 +04:00
</div>
Replace SASS with assets from Ghost-UI closes #2368 - Remove Ruby dependency (Gemfiles) - Remove sass/fonts from core/client/assets/ - Add copy task to Gruntfile to copy over ghost-ui assets - Install Ghost-UI via bower - Changed .npmignore/.gitignore - Remove grunt-contrib-sass dependency - Remove mentions of Ruby in CONTRIBUTING.md
2014-03-08 22:43:52 +04:00
</main>
</body>
Fix ghost-ui reference fixes #4072 - Correct reference to ghost.min.css
2014-09-19 22:31:21 +04:00
</html>
Reference in New Issue Copy Permalink