Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By summit on
Hi,
I have given up the category module (for this moment).
The reasons are the following:
- the module is too slow for production site
- the module is not enough maintained
- taxonomy-related module don't all work with the category module (like the taxonomy super select).
- it is staying a special module, instead of moving to core.
Especially the slowness of the module was to much lately.
I have a website which is being filled by people in development countries, and the website was to slow with the category module installed. They couldn't do the job correctly and I am now working on a solution for this.
Questions I have. How can I make dependencies (like the distant parent module in 4.6) without working with the category module?
I keep you posted on my further findings, but for now the websites will work without the category module.
Greetings,
Martijn
Comments
sad situation
i activated it too today..and am in deep trouble..wish i knew what to do.
dependencies:
You will need to write your own module.
About the slowness: categoreis are noddes. nodes are the best performing entities, yet only when cached. Did you try more aggressive caching?
Also: because they are nodes, other modules that hook into nodes, but do so in an ugly way (such as access permissions, badly coded image modules, badly coded filters and what more, there are plenty of them around) will have a severe impact.
I can advice you to re-check the speed issues with all other contributions, but the catgories, disabled. You may find that performance issues are actually not really caused by categories, yet only appear to be that.
Bèr
---
Professional | Personal
category or taxonomy
It is not only the speed. Of course you are right, and is category not only the slowmaking module.
Can you tell me how to cache the admin screens, so that adding a category will take less time?
What for me is a bigger problem, is the non-compatibility between the category.module and the taxonomy modules like taxonomy super select and taxonomy batch operations.
greetings,
Martijn
without category extreemly faster
Hi,
i am sorry to inform you that my website is extreemly faster without the category module.
Of course it can also be the interaction between TAC and the category module or something like this. But I am very happy with the performance without the category module.
Greetings,
Martijn
2 performance killers
Category has 2 performance killers. First, Node are resource intensive things. Much more so than normal taxonomy which just classifies nodes. This is the first slowdown.
Second, category does a number of sql queries more than once. This slows it down. I recently used it and had devel running. It showed there is a lot of room for improvement.
--
Matt
http://www.mattfarina.com
a bug
There is also a bug in category module that has it looking up the same sql query a number of times. This is a real slowdown. It could use some performance tweaking.
--
Matt
http://www.mattfarina.com
category nodes to taxonomy/term
Hi,
I am no buzzy with changing from category module back to taxonomy module. It is going ok.
The problem I have right now is related to the fact that categories are shown as nodes, so the menu items related to categories are node/{nr} instead of taxonomy/term/{nr}
Is there a possibility to easilly change the node/{nr} related to category-type to the right taxonomy/term/{nr}.
Now I have to go thrue the aliases and change them manually otherwise the menu items go to empty nodes because the category module is disabled?
Thanks in advance for your reply.
Greetings,
Martijn
good question
Sadly, my guess is that you need to do that manually unless you whip up some script to do it for you.
But, I'm no expert with the category module.
--
Matt
http://www.mattfarina.com