I had a good functional site prior to installing Category.module

I had a few defined categories using taxonomy.module

The reason I installed categories is because I wanted a tree like home page for my groups, just like http://groups.myspace.com/

Without adding any category.module content, I unistalled it, but with it went my prior set taxonomy categories,

Comments

jswaby’s picture

I was just about to go that route until I read this support request..

In fact, I can't uninstall category module because it depends on taxonomy, and taxonomy depends on category.

Is that another bug?

rimma’s picture

I got same problem because I want to try how powerful this module to organize categories.

I uninstall category module but I can no get other things back.
Currently, I plan to reinstall the whole site.
I think this module has changed many configurations during setup, even you uninstall it but it does not have function to restore your original configurations.
I am not sure if there is any better solution.

rimma’s picture

did you bring your site back?

stephen.idealso’s picture

Version: 5.x-1.1 » 5.x-1.0

Yikes, me too. I installed the category module, played with it for several hours. It is a great module and give lots of power to the relationships between Noes / Taxonomies / etc ... however:

I decided not to use it because it doesn't seem to work quite how I had hoped. When I disabled everything from the modules administrative section, I lost any taxonomy functionality entirely! Not only were the taxonomies I had before I installed the Category module gone when I installed it, but now there is no way to add taxonomy vocabularies, terms, or anything of the like.

As I said before, I really like this module, but it has really screwed up my site, and without a way to fix this, I'm going to have to completely re-install my site yet again.

The functionality that I couldn't find was rather basic (maybe). I wanted to have a a container of terms (call them formats), and if a format had a certain property (maybe a yes/no field in a node somehow), then it would allow for input into another field (call it location). Furthermore, I want both the Format and Location to be in the form of a drop down or select list with an "add another format" or "add another location" option that would give the user then an extra form to add a format or location. I'm trying to do this in as few clicks as possible for the user, so that they don't have to goto one page to add the format, another page to add the location, and then yet another form to put them all into the main content type (course). I'd like all of these to be on one form (making it very small with theming overrides).

But now the problem has developed into the breaking of Drupal, and I'm completely stuck as to what to do next.

Any help would be greatly appreciated!

Thanks in advance!

-S

rimma’s picture

I am considering how to bring the site back.
Just as stenphen said, this is a good module but currently it does not work very well with some core modules such as forum.
I just wish it can be better in the future.

jswaby’s picture

I was able to remove this module from my site on this newest upgrade (drupal 5.3), but I unfortunately had to lose all my taxonomy terms. I also had to delete all of the nodes category module created for my taxonomy terms, and the paths created by path_auto. Keep in mind that this module also creates a new taxonomy module (that is different from the one that comes in core) and a new book module (also different from the one that comes in core) (both .install and .module files for these). So the update made it easy to change back to the core versions of the module.

It was heartbreaking to lose all my tags and site structure, but i guess it's worth it to have a drupal install that is as close to core as possible.

jswaby’s picture

Title: Uniinstalling Category.module left me without any prior set Taxonomy categories » Uninstalling Category.module left me without any prior set Taxonomy categories
Status: Active » Closed (fixed)

Quite honestly, I don't think anyone will be doing anything about this. The module was designed to take over the taxonomy and book modules. So, unfortunately I don't think this is a bug...

I'm going to close the issue, but if anyone has issues with me closing the issue, please reopen it.

dex002’s picture

I've successfully reverted from my horrible experience with the Category module. On the Modules page, I disabled everything that depended on it as well as everything within the Category module itself. I then moved the Category module files out of my contrib modules directory. Then, I uploaded a fresh copy of the core Taxonomy module. (I didn't bother with the Book module as I never use it). After all that, my original taxonomy seemed in tact. Hope this helps someone

sammy-node’s picture

Thanks Dex002

Can confirm that problems reverting from Cat back to Taxonomy were solved by unselecting all the Cat modules and then deleting them from the "sites > all > modules" (or wherever your custom added modules are) and then copying the orginal core Taxonomy module files back into the "sites > all > modules" part and reinstalling it in the normal way that you'd install any new module.

j0hn-smith’s picture

I've deleted the category folder and reinstalled the taxonomy module which seems to have brought my taxonomy terms back but the links in a node to other nodes with the same terms have gone.

I'm really glad that I'm just testing Drupal, I would be really furious if this was a live site. There should be a warning about these problems on the main page.

ultimateboy’s picture

Component: Documentation » Code
Category: support » bug
Status: Closed (fixed) » Active

I do have a pretty big problem with closing this issue. I think that the problem is drastic. As a good starting point, documentation should be added on how to un-install this module. Modules are meant to be easy to install and un-install. They are meant to be add-ons to core, and not over-right code. So, while I agree that this module does some good, it should be coded in such a way that it does not harm the core modules (or at least allow for an easy un-install to get core back to core).

Just skimming through the issue queue I see several posts about un-installing this module. This tells me that something is wrong, modules should un-install without a hitch.

magickatt’s picture

I agree with UltimateBoy, there should be a message WARNING: THIS MODULE MODIFIES THE DRUPAL CORE or something to that effect, just so people are aware that removing it may not be straightforward (which seems to be the general concensus) because 'Bugs' just implies it may not work correctly, not that it'll fundamentally break your site...