NB: Original suggestions by Wolfey, John Bryan, jgsack, WorldFallz, eclauset, darumaki
In deprecated Usability forum http://drupal.org/node/64593

- The toggle button needs to be more common-place in the Drupal interface. The ability to easily turn features "on or off"

- Multiple select, check all/uncheck all
- For list forms with multiple columns: at the top (in header) a check all/uncheck all option
- Also a toggle option within the list to turn on/off a feature (click on, icon changes; then click off)

- Two areas identified: modules and permissions in admin area, possibly other lists.

- Especially with contributed modules list, the ability to disable for modules. Note, dependent modules would be auto-selected if parent module was selected. e.g, if CCK were selected it would select all dependent modules - then store note of which modules were disabled, and allow the user to 're-enable' just the ones which were enabled(?) (this is unclear- hj)

Comments

heather’s picture

heather commented

sorry, the original post is
http://drupal.org/node/164963

Modules: Is There a Way to Disable/Enable All of Them at Once?
Deprecated - Usability feedback · Drupal 5.x
Wolfey - August 6, 2007 - 15:56

spflanze’s picture

spflanze commented

It often happens that not all modules will be enabled on a Drupal site. This is the case with me because I will install many of them and then climb the learning curve on each new one before enabling it. So there is a need for the module admin page to remember which modules were enabled when they were last all disabled at once, and then be able to enable only those that were previously enabled. The memory should not only be in the database. There should be an option to store this in a file.

This is needed not just for Drupal 7. It is also needed for Drupal 5 and 6. Most of us are still using Drupal 5 because not enough modules have been upgraded to Drupal 6 and 7. When all modules are upgraded to Drupal 6 I expect it will be a while longer before enough of them are upgraded to Drupal 7. Maybe when that happens there will be a Drupal 9 to wait for module upgrades to :).

I have many modules. There are Drupal upgrades coming out several times a year. This is still true even for Drupal 5. The requirement to disable all modules before upgrading to a later version of Drupal means I cannot upgrade to every latest version of Drupal. This is because I do not have the time to disable and enable each module individually every time a new version of Drupal comes out.

ClearXS’s picture

ClearXS commented
Title: Usability: Multiple select, de-select, and toggles on list forms » Usability: Multiple Checking modsselect, de-select, and toggles on list forms
Component: usability » install system
Category: bug » feature

For over two weeks installing and having conflicts with mods and reinstalling again. As I got better in installing; that part is pretty quick, as I use the same modules dir. Would be horrible to upload and subtract up to 200 modules everytime... Probably the most work now is checking all mods. But I want to have the throttle all unchecked for core modules, none for security modules, and none for some basic modules that are in use with other modules. And all others checked for throttle.
It could be done automatically... -Good luck.

Another point is that I think all smaller modules should be put together to bigger mods, or combination mods / packages. It's really absurd to have 200 mods attached to my drupal; the more professional Drupal gets, the lesser mods of bigger size one should need?

And with conflicts, many mods cant be deinstalled and the site needs to be reinstalled, or changed back before some backup. I have no idea how the mod procedures could be made more secure in deinstalling. A practical 'down the drain' experience: http://drupal.org/node/357667

thedavidmeister’s picture

thedavidmeister commented
Version: 7.x-dev » 9.x-dev
Issue summary: View changes
Status: Active » Closed (fixed)
Issue tags: +Needs issue summary update

This isn't a solid proposal, it reads more like a "brain dump" and it's hard to see how much is relevant to the latest Drupal 8 (that does not allow toggling modules as is described here) #1199946: Disabled modules are broken beyond repair so the "disable" functionality needs to be removed.

Very likely that whatever this is, would have to wait to D9.

I'm closing this out. Feel free to update the issue summary and re-open if it's still relevant.

thedavidmeister’s picture

thedavidmeister commented

FYI - If you're a developer performing a major upgrade, there are two easy ways to enable/disable all modules at once:

1. Use drush, I recommend a bash script for repeatability
2. Use jQuery in the browser console + the normal UI

Version: 9.x-dev » 9.0.x-dev

The 9.0.x branch will open for development soon, and the placeholder 9.x branch should no longer be used. Only issues that require a new major version should be filed against 9.0.x (for example, removing deprecated code or updating dependency major versions). New developments and disruptive changes that are allowed in a minor version should be filed against 8.9.x, and significant new features will be moved to 9.1.x at committer discretion. For more information see the Allowed changes during the Drupal 8 and 9 release cycles and the Drupal 9.0.0 release plan.