Naz 076ad99593 Removed 500 error during production boot \w a theme error ... refs https://github.com/TryGhost/Team/issues/781 refs 813d288eb2# - The 500 error was introduced through a refed commit long time ago when (probably?) there were no other safeguards preventing from serving content through a theme with errors. Since than we have multiple safeguards when aploading/activating the theme with errors and the default handling when such error occurs is more graceful - a 400 with specific error details is shown - We need this change to land before bumping gscan that introduces more suphisticated error detaction in theme templates. Otherwise, people upgrading to new version and having an error on an unused template or somewhere undetected previously woul end up with a bricked site showing a generic 500 - not a great experience!		2021-07-02 14:31:45 +04:00
..
config	Moved theme config to new theme engine service	2021-04-21 14:21:32 +01:00
engines	Moved theme engines to new theme engine service	2021-04-22 21:05:01 +01:00
handlebars	Change to use @tryghost/logging	2021-06-15 15:59:11 +01:00
i18n	Change to use @tryghost/logging	2021-06-15 15:59:11 +01:00
active.js	Improved theme locale handling	2021-05-05 16:13:26 +01:00
engine.js
index.js	Moved activate from themes to the bridge	2021-04-27 13:52:19 +01:00
middleware.js	Removed 500 error during production boot \w a theme error	2021-07-02 14:31:45 +04:00
preview.js	Moved theme preview mw to new theme engine service	2021-04-24 19:56:00 +01:00