I use NAT to create terms in a specific vocabulary when nodes of particular type created. I am trying to use taxonomy_menu to populate those terms into my primary navigation but this doesn't work.

I don't see ANY errors in watchdog and tried different combinations of taxonomy_menu settings for the vocabulary.

I have few terms already created by NAT module in the vocabulary and enabled taxonomy_menu module after few terms were created with no change.

Are there any limitations (or does modules weight matters?) for this combination of two modules to work?
Or maybe you can at least point me what can be wrong?

CommentFileSizeAuthor
#4 vocabulary_settings.jpg172.55 KBivrh
#4 taxonomy_menu_settings.jpg191.55 KBivrh
#4 menu_view.jpg177.74 KBivrh

Comments

ivrh’s picture

ivrh commented

In fact - taxonomy_menu and menu_links tables contain all the rows I expected but the menu doesn't show them up.
I have tried "rebuild menu on submit" option as well.

I have also tried different vocabulary to the same menu as above and it works no problem!

indytechcook’s picture

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

I can see the node weight being an issue as the terms are being created from NAT. If the term is created before after taxonomy menu checks for new terms then it wouldn't know about the new terms.

Even so, the menu should have been created when you selected "rebuild." What are you using to display the list of terms? A view, the default taxonomy display or a custom callback?

ivrh’s picture

ivrh commented
Status: Postponed (maintainer needs more info) » Needs review

I can see the node weight being an issue as the terms are being created from NAT. If the term is created before after taxonomy menu checks for new terms then it wouldn't know about the new terms.

I can't see how this can happen, as terms created by NAT long before I even installed the module. By the time I activated taxonomy_menu for that vocabulary it already contained few terms. The way you describe here may only affect automatic synchronization of newly created terms

Even so, the menu should have been created when you selected "rebuild."

Tried this many times with no luck

What are you using to display the list of terms? A view, the default taxonomy display or a custom callback?

Using browse terms functionality by default provided by taxonomy module (/admin/content/taxonomy/3), as well as menu page (at /admin/build/menu-customize/secondary-links)
As described - I browse tables directly (via PHPMyAdmin) and all menu items are there, but they don't appear in the menu itself (at /admin/build/menu-customize/secondary-links). I also checked other menus (just in case if my links in other menu) - but they are not there as well.
Clearing website cache doesn't do much as well.
Again - whey using taxonomy_menu with any other vocabulary - I can see links in taxonomy view right away

Can't see any reason why it doesn't work

ivrh’s picture

ivrh commented
StatusFileSize
new menu_view.jpg177.74 KB
new taxonomy_menu_settings.jpg191.55 KB
new vocabulary_settings.jpg172.55 KB

Attaching screenshots

indytechcook’s picture

indytechcook commented
Status: Needs review » Closed (duplicate)

Thanks ivan, the screenshots told me exactly what I needed to know. The issue is with the option that adds the "all" at the end is causing the issue. It's related to this issue: #426304: [NOT SOLVED] Hierarchical menu, NOT expaning to current term. See Comment 30 and Comment 32. I had this same issue, even if I add the menu link manually in the menu (without using taxonomy menu). It seems to be related to a bug with core.

I'm setting this issue as a duplicate. Please watch the other issue for updates.

Thanks,
Neil

stefan81’s picture

stefan81 commented