Let's say I have in my admin modules page one.module, two.module and three.module. Let's also say that one.module depends on two.module and that two.module depends on three.module. Now I go to my admin page, and, being lazy, only click on three.module, because I know the other two will be automatically enabled.

What actually happens is one.module does not get enabled, and two.module ends up being in an odd state that the system doesn't correctly identify or know how to deal with.

This can be seen by installing the E-Commerce suite of modules and enabling one or more of the API modules in the E-Commerce Core group.

Comments

chx’s picture

chx commented
Title: Module dependency does not work more than one level deep » Change dependencies checker a complete one
Version: 5.0-rc2 » 6.x-dev
Assigned: Unassigned » chx
Category: bug » task

This needs a DFS, an implementation of which already sits in my sandbox. Too late for Drupal 5.

Conditi0n’s picture

Conditi0n commented
Assigned: chx » Unassigned
Status: Active » Closed (fixed)

The Drupal 6 works on any level of dependency, although the implementation is naive and is not the fastest. In Drupal 7 it contains a proper DFS implementation in 'graph.inc'.