Install og, og_vocab, views, and views_rss then try to disable all these modules. You must...

  1. Uncheck og_vocab, hit Save configuration
  2. Uncheck og, hit Save configuration
  3. Uncheck views_rss, hit Save configuration
  4. Uncheck views, hit Save configuration

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

RobRoy’s picture

Version: x.y.z » 5.x-dev

Correct version.

danbh’s picture

This bug is related to the other bug you filed:
http://drupal.org/node/93779

danbh’s picture

Personally, 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

ricabrantes’s picture

Status: Active » Closed (duplicate)
dman’s picture

I 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...

kenorb’s picture

Component: update system » system.module