Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I like the simplicity of this module, I only wish it could be used for disabling modules as well.
It's common practice to import database dumps from the production site to your development site, to keep it in sync. Escpecially if you have a workflow like local -› dev -› stage -› prod, where changes to the codebase flows upstream and database dumps go downstream.
In a scenario like that, you often have modules that should only be enabled on prod, e.g. Varnish and Backup & Migrate, or modules that should not be enabled locally, e.g. Memcache or Google Analytics. Those modules will be enabled in the database dumps from prod, leaving you with the task to disable them each time the database travels downstream.
Being able to disable modules would make this module twice as nice :)
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | disable-modules-1350364-3.patch | 523 bytes | valderama |
Comments
Comment #1
ximo commentedMeant to assign it to myself, I'll give it a try later.
Comment #2
sbilde commented@ximo , I agree! - This would be a nice feature to this really handy module.
Comment #3
valderama commentedI made a quick working patch. Would me nice if someone could review, to get this into the module..
Best,
walter
Comment #4
miikamakarainen commentedI have reviewed the patch and commited the changes.
Comment #5
valderama commentedWow, thanks - that was fast!
Comment #6.0
(not verified) commentedUpdated issue summary.