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
..
client@70dac42ffd	Updated Admin to v4.17.0	2021-10-01 16:00:30 +01:00
frontend	Added description to allowed preview params	2021-09-30 14:07:28 +01:00
server	Fixed inconsistent theme settings state after toggling customThemeSettings labs flag	2021-10-04 11:23:46 +01:00
shared	Removed labs gating from bulk action endpoint	2021-10-01 14:17:52 +02:00
app.js	Added Sentry to new boot process	2021-02-19 09:20:41 +00:00
boot.js	Moved routing setting hash calculation to backend	2021-09-28 04:59:41 +13:00
bridge.js	Added clarifying note to bridge	2021-09-30 15:43:39 +01:00