Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
The main drawback of this module is that you end up with lots of modules installed that aren't doing anything.
Proposed resolution
Add a post-post update that:
- finds installed update modules
- uninstalls them
- adds them to a variable (using variable_get()/set() for now) so that they don't get re-installed.
Also ensure the before/after installs check that variable before they install anything.
Remaining tasks
User interface changes
API changes
Data model changes
Comment | File | Size | Author |
---|---|---|---|
#6 | dum-rum-2655340-6.patch | 5.97 KB | plach |
Comments
Comment #2
plachHere's a patch implementing the proposed solution and an additional
drush rum
command that will remove uninstalled DUMs. Actually it will move them to aremoved
subdirectory and rename.info
files to.info.removed
so they will no longer be detected as modules.Comment #3
plachActually, I didn't realize DUM is already keeping track of seen modules. Refactored the previous patch to use that instead.
Comment #4
plachOne more little fix, we should be good now
Comment #5
marco CreditAttribution: marco at Tag1 Consulting commentedReviewed and tested, this works well.
Comment #6
plachActually it seems drush can pick up the
.drush.inc
code even before the module is enabled, which makes the update fail because the.module
is not enabled yet. This updated patch takes case of that.Comment #7
marco CreditAttribution: marco at Tag1 Consulting commentedI've verified the issue mentioned above can happen, and that the change prevents it.
Comment #9
plachCommitted and pushed, thanks!