Updated: Comment #0
Suggested comment message
Issue #2082117 by alexpott, xjm, tim.plunkett, heyrocker, beejeebus, sun: Fixed Install default config only when the owner and provider modules are both enabled.
Since this was split from the meta issue.
Based on various IRC discussions with alexpott, xjm, mtift, and others, this is a sub-issue ofthat focuses exclusively on what happens to configuration entities when modules are installed. Many of the problems are discussed in that other issues. The options are basically to install default config or not.
Please note thatcovers the topic of uninstallation.
One suggestion is to only install default config when both the providing module and the config entity defining modules are (or will be) installed. The proposal is to create a new ExtensionInstallStorage class that extends InstallStorage and that can be used in config_install_default_config() to determine if an extension provides default configuration for any other enabled extensions. This is the approach used in.
Decide what to do when a module is installed that provides default configuration that uses another module's API
User interface changes
None. However, this patch might enable changes to the UI during module installation.
|PASSED: [[SimpleTest]]: [MySQL] 58,973 pass(es). |
[ View ]
|PASSED: [[SimpleTest]]: [MySQL] 59,229 pass(es). |
[ View ]