Add link to disable non-required core modules for upgrading
Senpai - September 6, 2007 - 17:28
| Project: | Drupal Administration Menu |
| Version: | 5.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
How hard would it be to write a sql query that selected all modules that didn't start with 'modules/', and were also STATUS = 1?? I'm imagining a button that would disable all non-core modules for the site, in preparation for an upgrade.
To take this even further, if each contrib/custom module's name & status was saved into a db field before the site was upgraded, reversing this process after the upgrade would be a hell of a lot less painful as well, dontcha think?
#1
I will do this one.
#2
Good idea!
Steps to implement:
util_modules_disabledis not set).util_modules_disabledutil_modules_disabledutil_modules_disabledvariable.#3
The 5.x version of this module is effectively dead, so let's focus on the 6.x branch for future development.
#4
I have implemented a quite similar feature into Drupal Administration Menu that allows to disable/re-enable all "developer" modules in one fell swoop. Doing this one should be quite easy, and I really would like to provide this feature to the grand crowd of admin_menu users.
Thus, moving over to admin_menu's queue. And because that would really help folks trying to upgrade from D5, I'm hereby downgrading this issue for 5.x.
#5
Better title.
#6
I totally love this idea! admin_menu it is then! I use admin_menu on every one of my sites anyway, and encourage everyone else to do so.
#7
I think starting with 6.x all updates will run even if the modules are disabled - i.e. there may be no point to implementing this for 6.x.
#8
No no, Peter, this would be for core upgrades so contrib modules can all be disabled before the event. You wouldn't want a 5.x contrib active after you upgraded core to 6, would you?
#9
Well, pwolanin actually tried to say: It does not matter if contrib modules are enabled or disabled during an upgrade to D6. All update functions in all install files will be executed during an upgrade.
However, that sounds really scary. Can anyone confirm this behavior? If this is really the case, this issue does not make sense at all.
#10
Why not create a menu that disables all modules prior to upgrading since this has to be done anyway, the admin menu is perfect for this.
#11
@darumaki: See comment #9.
#12
oh I see, so when upgrading to 6 we didn't have to disable the modules ?