I've encountered unexpected behavior with Taxonomy Menu when the "Syncronise changes to this vocabulary" and "Auto Expand Menu Item" options are enabled on a vocabulary.

I created the menu for the vocabulary using the custom path option, assigned it to an existing menu with several existing items and then moved the newly created menu items to nest as 2nd level items under one of the menu's pre-existing top level items.

After that, whenever I create a new story and assign it to one of the taxonomy terms, the related menu item moves itself to the top level of the menu hierarchy and sets itself as auto expanded.

My assumption -- perhaps incorrect -- was that "Syncronise changes to this vocabulary" referred to additions or subtractions from the list of terms in the vocabulary -- not to additions to the number of content items that were tagged with an existing vocabulary term. BTW, the "Display Number of Nodes" check box is NOT enabled under this scenario.

I'm running Drupal 6.10.

I've managed to avoid the problem by disabling the "Syncronize" and "Auto-expand" options -- but it sure had me baffled for a while.

Thanks for a very handy module!

Comments

indytechcook’s picture

indytechcook commented

Synchronize changes to this vocabulary means that if you add a new term or change (or change the term/node relationship when using diplay count) then the menu will automatically update.

Auto Expand means that the menu item is build the the "Expand" option set to TRUE.

It should be doing this in either way. I"ll give it a test

indytechcook’s picture

indytechcook commented

Can you try the latest DEV version?

ermannob’s picture

ermannob commented
Version: 6.x-2.3 » 6.x-2.x-dev
Component: User interface » Code

Hi indytechcook and Bill,
I'm having the same issue... I tried also latest dev.
However my setup is a little different: "Syncronise changes to this vocabulary" and "Hide Empty Terms" are on. Other options are off.
I tried 2.3 stable, 2.3 with i18n patch, dev version.
If I "Select to rebuild the menu on submit" the menu goes back to the right hierarchy.
On node insert or modify, the menu hierarchy breaks. It doesn't happen always. Frequently. (maybe it has to do with caches?)

ermannob’s picture

ermannob commented

I just got aware that modules "Taxonomy Menu Custom Path" and "Taxonomy Menu Hierarchy" were turned off. Only "Taxonomy Menu" was on.
Don't know if that was the problem. I'm waiting for something to happen on my menu.

ermannob’s picture

ermannob commented

The problem is still there. Investigating...

ermannob’s picture

ermannob commented

My suspects are on i18n. I think i18n's Taxonomy syncronization is hurting taxonomy menu, but I don't know how.

@Bill: were you using i18n too?

ermannob’s picture

ermannob commented

The bug occures exactly when I save a translation for a node (example: http://localhost/drupal/it/node/add/content_type?translation=477&languag...).
For some reason I don't know, after saving the node at that URL, taxonomy menu shows that node's category as if it was at first level. But it's not, it's at second level deep.
I have to rebuild the menu to get it ok again.
Please note: I'm using 2 different vocabularies for 2 different languages. Terms are not synchronized between node translations.

ermannob’s picture

ermannob commented

I'm looking for help also at i18n: #517652: Conflict with taxonomy_menu

arlinsandbulte’s picture

arlinsandbulte commented
Status: Active » Postponed (maintainer needs more info)

TM 6.x-2.5 contains a bunch of bug fixes and new features. I think some of them are related to this.
Can anyone confirm if this is still valid?

ermannob’s picture

ermannob commented

Sorry. I still have this issue... :-(
I'll try to dig some more to get more info.

arlinsandbulte’s picture

arlinsandbulte commented
Status: Postponed (maintainer needs more info) » Fixed

2 months of inactivity while status was at "postponed (maintainer needs more info)"
Marking as fixed. Feel free to re-open if you still require help here.
Please provide some more information if you can and mark as 'active.'
Thanks.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.