Followup to. Themes now have an installation status but there is no way to uninstall them - we can only disable them. This puts a theme into limbo where the theme can not be used but configuration that is dependent on it is still in the active store. Like modules, themes must now clean up their installed configuration when they are uninstalled.
- Make theme enabling and disabling the same as the module subsystem following . In HEAD (and D7) themes are a two state system (disabled or enabled) - in some ways this patch just changes the system use the same language as the module system.
- Remove associated configuration entities when a theme is uninstalled eg block configuration entities.
- Replace enable/disable in the UI with install/uninstall. Since themes are a two state system this change does not really change any user interaction.
The effects of the consolidation of ThemeHandler and ModuleHandler operations can be see in the ConfigImporter - this patch has several simplifications to that class.
User interface changes
- UI text changed from enable/disable to install/uninstall
- CSS classes changed from system-themes-list-enabled/disabled to system-themes-list-installed/uninstalled
- ThemeHandler::enable() replaced with ThemeHandler::install()
- ThemeHandler::disable() replaced with ThemeHandler::uninstall() and add call to ConfigManager to remove configuration and the theme's dependencies
- Replace hook_themes_enabled() with hook_themes_installed()
- Replace hook_themes_disabled() with hook_themes_uninstalled()
- Remove disabled key from core.extension configuration
- Route names are change to reflect to move to install/uninstall
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 76,273 pass(es). View
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 76,260 pass(es). View
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 76,336 pass(es). View
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 76,187 pass(es). View