Voting starts in March for the Drupal Association Board election.
Updated: Comment #94
It is unclear what should happen to configuration entities (configurables) when installing and uninstalling a module that contains configuration connected to another module's API
- Views allows modules to provide default views
- views_test_config.module has its own config directory and its own default views
- The config files are in Views' namespace, and "belong" to it
- uninstalling views_test_config will not remove its config. Only uninstalling views.module will do that
In part because this issue is blocked onand in part because we want to limit the scope of this issue, we have decided to make this issue a "meta" issue by creating two child issues:
If a module creates a node type, for example the Forum module creates a node type of forum. Then is up to the module to decide if this remains after uninstalling if there are no dependencies. For example, it is entirely reasonable to install forum, get the vocab, get the content type, create content, then uninstall forum and build a new forum listing with views or whatever.
Determine when configurables are installed and uninstalled.
User interface changes
FAILED: [[SimpleTest]]: [MySQL] 58,527 pass(es), 3 fail(s), and 20 exception(s). View
FAILED: [[SimpleTest]]: [MySQL] 58,410 pass(es), 124 fail(s), and 27 exception(s). View
FAILED: [[SimpleTest]]: [MySQL] 58,303 pass(es), 153 fail(s), and 64 exception(s). View
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch config-1776830-53-tests.patch. Unable to apply patch. See the log in the details link for more information. View