This module is EXACTLY what I need. . .provides a nav menu based on a nested hierarchy of terms.
Perfect! I can even use the "Default" "Menu path type" and it runs through my aliases aworks out the human friendly URLs instead of all those meaningless numbers.
It all looks like it's working flawlessly

The problem is I can't get Taxonomy Menu to run through the whole vocabulary!
It'll get through 50 terms one time, 60 the next I've had it go as far as 81 but then it stops.
I can leave the moving status bar on the "REBUILDING TAXONOMY MENU" page forever but when I check the numer of menu items created in the db table "menu_links" it's stuck at 92 this time around.

This site and the vocabulary I'm working with has about 20 main taxonomy terms and each has a a bunch of sub terms under it.
There are about 200 terms in the vocabulary altogether.

Each time I run through the process checking the "Select to rebuild the menu on submit." checkbox I get a different number of taxonomy terms processed into menu items. This seems to tell me that the module isn't breaking because of a wierd character in a term or because of a loops caused by my aliases or something.

It seems to be telling me that the process is timing out or something.

I have tried both version 2.9 and 2.x-dev with the same results and I've also set

max_execution_time = 320
max_input_time = 320
memory_limit = 256M

but that's about the limit of my understanding of which parts of the machine I can and need to tune to make this work.

Any help would be greatly appreciated, surely a 200 term vocabulary isn't too big for Taxo Menu?

Comments

austintnacious’s picture

Category: support » bug
Priority: Major » Critical

Nothing? No one has any idea why Taxonomy Menu stops generating menu items after 50-90 links?

dstol’s picture

Category: bug » support
Priority: Critical » Normal
Status: Active » Fixed

In my test site I am using a vocabulary with 600 terms.

Page execution time was 237.68 ms.
Memory usage:
Memory used at: devel_init()=1.57 MB, devel_shutdown()=13.09 MB.

It's well within the limits of your hosting. It could be your MySQL settings, I'd look into max_allowed_packet, but that's really outside the scope of this issue queue.

austintnacious’s picture

Status: Fixed » Active

Bro!

I'll give you the "support request" since I did start this thread as a "support request" but it is not "FIXED" and I am still looking for help which might eventually lead to the discovery of a conflict or a bug or a task that might improve the module in the long run. Eh!?

[Please] Do not change the status to "fixed" until you or someone else has come up with a satisfactory explanation or process to determine why Taxonomy Menu is not working on my site.

I freely admit to being a dumb-ass end-user. We can't all be the god-like creators of such classics as "Killswitch". . . if we could the sun wouldn't shine so brightly out of your asshole, would it? Just kidding!

But don't you gods develop and maintain modules to make life easier for dumb-ass end-users like me? And don't 1000s of us dumb-ass end-users host our sites on affordable shared hosting? And isn't all that the whole effing point of Drupal and open-source software?

My site is running many other important, heavy-lifting modules (including Devel), all of which work flawlessly!

The ONE, SINGLE module which does not run flawlessly and which is preventing me from completing this project is Taxonomy Menu and I'd like to know why since it does exactly what I need it to do and what it outputs before it gets stuck is perfect!

But it does get stuck while nothing else on this site gets stuck.

Therefore, pretty much BY DEFINITION, there is a problem with Taxonomy Menu.

This FACT should concern you as the maintainer of the module; there is a real world useage case of your module NOT WORKING alongside dozens of its peers which ARE WORKING.

Do you get me?

I am happy to provide you (or someone else who does not just want to dismiss the issue with the minimum possible effort) with whatever other diagnostic info that I can provide.

Whether it turns out to be a conflict with another module or a limitation with the shared hosting environment where this site lives my issue indicates a problem with Taxonomy Menu!

I.e it might me the source of the energy which creates the light which shines out of your ass in the lab but it isn't robust enough to survive out in the wild [, under certain conditions which my site appears to present]. The module does work but it does not complete its task.

You are not maintaining this module as some theoretical experiment are you?

Now, I too have Devel installed and can provide all of the information that is available to mere-mortal dumb-ass end-users operating on shitty shared hosting accounts through Devel, phpMyAdmin, Watchdog, phpinfo() etc..

What I cannot do is change the shared reality in which I presume we both operate; you develop / maintain a module which you want people to use, many of those people operate in shitty but affordable shared hosting environments where they have no access to change max_allowed_packet in the hope that it might allow Taxonomy Menu to thrive.

Get me?

austintnacious’s picture

Title: Desperately need help with Taxonomy Menu time outs maybe? » Desperately need help with Taxonomy Menu time outs -> Conflict with JQuery 1.5 and / or JQuery Update 6.x-2.0-dev
Version: 6.x-2.x-dev » 6.x-2.9
Component: Code » Documentation
Category: support » task
Priority: Normal » Critical

So I tracked my problem with this issue and my other Taxonomy Menu issue to an incompatibility / conflict with Jquery Update module version 6.x-2.x-dev / Jquery 1.5.

This was also causing an issue with IMCE (http://drupal.org/node/1493416) on my site and both problems seemed similar, i.e. the page was waiting for some info coming back from the server / waiting for a process to complete on the server and that info wasn't getting back to the page.

Anyway, in tracking down the IMCE problem I also have my main Taxonomy Menu issue fixed.

So, to those who are experiencing this issue check admin/reports/status for your JQuery version and admin/reports/updates for your JQuery Update version. If you have a JQuery version higher than 1.3.2 and/or JQuery Update module version higher than the "recommended" 6.x-2.0-alpha1 bring those two back to the versions stated here and you should find this issue resolved.

I don't remember why I went up to JQuery 1.5 / JQuery Update 6.x-2.0-dev but I did and it breaks Taxonomy Menu.

I now see this as an 'undocumented incompatibility' the documentation of which I regard as quite "critical" (this haas cost me over a week of delay) so I've made the appropriate changes to the issue settings above.

Barrett’s picture

@austintnacious: I'm glad you were able to work out your issue. If you could help by providing some language that you think would convey the problem, its source, and the resolution to other users, I'd be glad to incorporate it into the documentation.

austintnacious’s picture

Well, simply put the 6.x-2.x version of taxonomy menu does not appear to work on sites using JQuery 1.5 / JQuery Update 6.x-2.0-dev.

At least it didn't on my site(s), downgrading to JQuery 1.3.2 / JQuery Update 6.x-2.0-alpha1 solved this problem (and a similar problem with IMCE).

Now that seems to me to be a "dependency" and a dependency on specific library / module versions.

That dependency (if it does indeed exist) should be noted on the taxonomy menu project page, in the readmes and on /admin/build/modules, right?

If this is not a "dependency" per se then the conflict with the higher versions of JQuery / JQuery Update should be noted somewhere as a courtesy to other users who might find themselves using JQuery 1.5 / JQuery Update 6.x-2.0-dev and having problems with Taxonomy Menu but not managing to make the connection.

I'm sure I must have upgraded to JQuery 1.5 / JQuery Update 6.x-2.0-dev for a reason and for all I know now there may be some other aspect of my site which isn't working now because of another module's dependency on the higher versions of JQuery 1.5 / JQuery Update 6.x-2.0-dev. Dilemmas like this would be good to know upfront.

I don't know the nuts and bolts of how menus are built in Drupal. Now, as I think back and look back at the modules in question I don't see any mention of JQuery Menu. I am using JQuery Menu to make my Taxonomy Menu block expandable. I thought I remembered explicit suggestions for using JQuery Menu to make Taxonomy Menus expanadble but now I don't see any mention of that, so maybe I was dreaming.

Maybe the problem arises there but since my problem came up on the "REBUILDING TAXONOMY MENU" page after selecting to "rebuild the menu on submit" on /admin/content/taxonomy/edit/vocabulary/x in my simplistic view of things the problem / conflict / dependency resides with Taxonomy Menu.

dstol’s picture

Title: Desperately need help with Taxonomy Menu time outs -> Conflict with JQuery 1.5 and / or JQuery Update 6.x-2.0-dev » jQuery 1.7.1 breaks batch api
Project: Taxonomy Menu » jQuery Update
Version: 6.x-2.9 » 6.x-2.x-dev
Component: Documentation » Code
Category: task » bug

I'm inclined to think that since taxonomy menu makes no use of jquery, perhaps the 6.x-2.x-dev version of jquery update may have broken something in core, like batch processing. This actually seems to be the case. I downloaded jquery update, enabled jquery 1.7.1 and ran a batch (node access rebuilding, if you're interested) which failed spectacularly.

Related so may be a duplicate of your issue #1507682: JQuery Update 6.x-2.x-dev / Jquery 1.5 has serious incompatibilities with other modules that REQUIRE documentation or more likely #1067290: Fix jQuery 1.7 for Drupal 6.

Aside: I'm also interested, since in jquery update 6.x only supports jquery 1.3.2 or 1.7.1 (see http://drupalcode.org/project/jquery_update.git/tree/refs/heads/6.x-2.x:...), how you are running jquery 1.5? This could be also be the problem.

sumaiyajaved’s picture

oh my god ... I had been banging my head, pulling my hair and have actually injured my hand taping on the mouse working on batch api to import books from csv.

Just couldnt understand why a simple script is not working for me. Then I realized because of jquery 1.7. I had used jquery update on my drupal 6. and had to remove it to make life worth living. Drupal guys pleeeease work on your documentation ..

markhalliwell’s picture

Status: Active » Closed (outdated)

Drupal 6 reached EOL (end-of-life) on February 24, 2016.