Ghost/core/server/services/themes
Kevin Ansfield 25b0657784 Fixed inconsistent theme settings state after toggling customThemeSettings labs flag
no issue

If Ghost was booted or a theme activated with the `customThemeSettings` flag disabled but with a theme that has custom settings, enabling the flag later on wouldn't show the settings in Admin or make the settings available in the front-end. Similarly, disabling `customThemeSettings` when Ghost had been booted/or theme activated with it enabled meant that settings were still available on the front-end.

- added an event listener for `settings.labs.edited` that fully re-activates a theme so that it's passed through gscan again and the custom theme settings passed back are included/excluded based on the flag value and any required settings sync with the database is performed
2021-10-04 11:23:46 +01:00
..
activate.js Rework the themeService public API 2021-07-07 15:02:02 +01:00
activation-bridge.js Added syncing and theme exposure of custom theme settings (#13354) 2021-09-23 12:44:39 +01:00
index.js Fixed inconsistent theme settings state after toggling customThemeSettings labs flag 2021-10-04 11:23:46 +01:00
installer.js Removed i18t dependency from installer module 2021-09-03 20:33:28 +04:00
list.js Moved theme service to core/server 2021-04-27 15:14:49 +01:00
loader.js Refactored theme service to use async/await 2021-07-07 12:28:55 +01:00
storage.js Fixed test for overriding active theme 2021-07-11 20:02:32 +01:00
ThemeStorage.js Corrected type declarations in ThemeStorage 2021-09-22 14:16:39 +02:00
to-json.js Moved settings/cache to shared/settings-cache 2021-06-30 15:49:10 +01:00
validate.js Added syncing and theme exposure of custom theme settings (#13354) 2021-09-23 12:44:39 +01:00