Voting starts in March for the Drupal Association Board election.
Updated: Comment #44
Import process cannot handle modules being enabled/disabled. This issue was discussed at length in Prague. The UI with respect to synching configuration probably needs to special case enabling and disabling of modules. Anything that triggers data deletion needs to notify the user. This is related tobut we should remember that during config import that core only support importing a complete config tree.
Make the configuration import a 2-step process: (1) handle any module changes, then (2) do the current import process. Account for the various scenarious outlined in #31
- (done) Waiting on
- (ongoing) open follow-up and "good idea" issues found while working on this issue
- check to make sure all follow-ups and related issues were opened (remove the needs tag when that is done)
User interface changes
Blockers of this issue
Follow-ups needed because this was committed:
Spin off to separate issues
Good ideas of separate parts discussed or found during this issue, but did not blocking this, and might have been done even if this issue had not been fixed (not follow-ups)
- (noticed as a result of this being a committed, but already an existing issue)
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 67,505 pass(es). View
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 67,553 pass(es). View