mirror of
https://github.com/TryGhost/Ghost.git
synced 2025-01-27 22:49:56 -05:00
25b0657784
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 |
||
|---|---|---|
| .. | ||
| adapter-manager | ||
| auth | ||
| bulk-email | ||
| email-analytics | ||
| integrations | ||
| invitations | ||
| invites | ||
| jobs | ||
| mega | ||
| members | ||
| notifications | ||
| permissions | ||
| posts | ||
| public-config | ||
| redirects | ||
| route-settings | ||
| settings | ||
| themes | ||
| webhooks | ||
| custom-theme-settings.js | ||
| limits.js | ||
| oembed.js | ||
| slack.js | ||
| users.js | ||
| xmlrpc.js | ||