Closed (duplicate)
Project:
Drupal core
Version:
5.x-dev
Component:
system.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Nov 2006 at 07:53 UTC
Updated:
27 Jan 2009 at 19:49 UTC
Install og, og_vocab, views, and views_rss then try to disable all these modules. You must...
We should deal with disabling modules in the same way as enabling. Let the user uncheck what he or she wants, then check if we are messing up a dependency by disabling the given module(s). If so, throw a confirm screen (just like the enable confirm screen) saying, if you want to disable og, you must also disable og_vocab, do you want to disable this module as well?
Comments
Comment #1
RobRoy commentedCorrect version.
Comment #2
danbh commentedThis bug is related to the other bug you filed:
http://drupal.org/node/93779
Comment #3
danbh commentedPersonally, I agree that enabling should be the same as disabling, but I disagree that the current method for disabling is the better one. I personally like the greying out of modules if changing it will cause dependency problems.
If you use an automated method, I worry that a mistake could be made by the automation, which RobRoy already discovered in http://drupal.org/node/93779
Comment #4
ricabrantes commentedDuplicate http://drupal.org/node/93779
Comment #5
dman commentedI just removed ecommerce from a site (dev)
Man it was tedious.
At least 6 goes at turning things off before other things could be removed...
Comment #6
kenorb commented