Quoting Peter Wolanin <pwolanin@gmail.com>:
Earnie, I don't think you are correct on this point. In Drupal 4.7.x, a module was included even when disabled only on the /admin/modules page. In 5.x, it should never be included.
http://api.drupal.org/api/5/function/module_load_all http://api.drupal.org/api/5/function/module_list
-Peter
On 6/13/07, Earnie Boyd <earnie@users.sourceforge.net> wrote:
I haven't looked to see the changes yet for D6 but for D5 the module is included even if it is disabled. This also violates my sense of what "disabled" means. I've been bitten by this before.
I stand corrected. Maybe it was prior release versions where I experienced this issue. I have a patch in the issue queue for breaking out module_list to module_list_all and module_list_bootstrap because bootstrap calls module_list twice and pulls from the DB twice with $refresh set to TRUE. Reference http://drupal.org/node/116820 for more information on that. Earnie