This originally started with what I thought was an 'Acidfree' problem, but soon discovered it to be a combo of 'Acidfree' and 'Category' (http://drupal.org/node/145740) ... check out the link for more info.

That issue aside, my beef is how 'Category' just decides that it will edit the dependencies of another, namely 'Taxonomy'. I'm sorry, but that is just poor coding practises, as a prof used to say "you don't play with someone else's balls" (pardon the rudeness, it's a direct quote).

Anyway, apparently when 'Category' is installed it edits the 'Taxonomy' module's dependencies ... so you've got 1 module editing the dependencies of another. By default, the 'Taxonomy' module is in the base module dir (`/modules/taxonomy/`) ... but to do multi-sites "properly", I put 'Category' in `/sites/all/modules/` ... so if I want one site to use 'Category' and another to not, I'm pretty much screwed ... my goodness!!

Is there any way around this?? There has to be.

Comments

Brantone’s picture

Brantone CreditAttribution: Brantone commented

Please note, I am aware of the multi-site tips, as provided on:
http://category.greenash.net.au/node/135

My main 'issue' is the fact that 'Category' is telling another module that they're now dependent on 'Category'. I recognize that currently for things to work properly this has to be done, but if I had the time I'd search out an alternative because as I mentioned, that's not very wise coding practise because as shown with adding another module to the mix (in this case 'Acidefree') it is causing quite a lot of problems!