Here are the steps to reproduce the bug:
-Install new Drupal instance using Drupal 5.1 and the Category and Taxonomy modules already present.
-On the fresh, new instance, go to Home > Administer > Site Building > Modules.
-Notice how the checkbox to the left of Category is grayed out. Notice how all other modules that depend on Category say it is disabled. Also notice how Taxonomy is selected by default.
-Enable one other module. In my case, I enabled poormanscron.
-Notice how Category is now enabled. While the checkbox is checked, it remains grayed out. All modules that depend on Category now indicate that Category is enabled.

Comments

aren cambre’s picture

aren cambre commented

Who knows, but unlikely this was a Category module issue.

JirkaRybka’s picture

JirkaRybka commented

I've never encountered this sort of a problem. Doesn't it have something to do with wrapper modules? i.e. Taxonomy wrapper replaces Taxonomy, and depends on Category. The wrapper shouldn't be installed by default, but since the installation is just renaming files, if I copy the codebase back from a site where the wrapper was already installed, it's not the same as if I install a fresh Category package.

I'm just guessing here, though, and I'm mostly testing on 6.x too - so take this as a mere suggestion where to check:
- Are you sure you put a fresh Category package to the site (not a copy from another already working site)?
- What is shown for Taxonomy on modules page: Depends on Category, or no dependency?

aren cambre’s picture

aren cambre commented
Status: Active » Closed (fixed)

Whoops, meant to close this issue. It's very old, and I think I misinterpreted when I reported it 2.5 years ago.