I apologize if this was answered before, but I could not find any hint on how to solve the problem.
After upgrading to version 2.x, the vocabulary page links (the ones that previously would lead to a summary page with the list of all content tagged within the vocabulary) were changed from "category/vid" to "taxonomy/term/". This path leads to 404.
I have disabled-uninstalled-enabled the module several times, each time updating DB tables and rebuilding menus on creation, but the problem persists. This also reproduces on newly created taxonomy menus.
What am I doing wrong? Shall I enable the Hierarchy and/or custom path submodules?
Is there a workaround to restore the path of the vocabulary menu item in order to link to a vocabulary page with title=vocab name, listing all content within the vocab?
Thanks in advance.
Comments
Comment #1
indytechcook commentedDo you have any terms attached to that vocab?
For the vocab item it is supposed to use the path of 'taxonomy/term/tid tid tid tid' with all of the tid's for the vocab.
Comment #2
Anonymous (not verified) commentedI've got the same problem like bohz: With the upgrade from version 1.02 to version 2.1 the "root" link for each vocabulary only shows "/taxonomy/term" which results in an 404-error.
I have a hierarchical vocabulary and no idea...
Thanks
Stefan
Comment #3
indytechcook commentedWhich path type are you using? What options do you have enabled? How Can I reproduce this?
Comment #4
my-family commentedI have the same problem. Menu path type: Default. Terms and nodes are created, but Vocabulary path goes to 404.
(In addition: when I change the Menu path type to Hierarchy or Custom path, the whole menu disappears).
Thanks in advance for help.
Comment #5
bohz commentedHI!
I have terms attached to the vocab (5 to 7). it's a single level hierarchy.
Actually, after the first upgrade to 2.x, the vocab path was indeed "taxonomy/term/tid tid tid tid", but since this path would output a vocab page which title clustered all terms together (not nice), I thought there was some kind of error.
So I went to unable-uninstall-enable the module several times, resulting in the path changed to "taxonomy/term/" only (please note the final slash).
I tried to enable the hierarchy and custom path sub-modules but I wasn't able to configure them in order to show something (the menus did not show up). So I disabled them.
I guess I have to clean up the DB tables (by hand?) once more.
Is there a way to have the vocab summary page titled with the name of the vocab, instead than with the list of terms?
Thanks a lot!
Comment #6
indytechcook commentedThanks for the info. I'll get this fixed after work tonight.
Comment #7
Anonymous (not verified) commentedI'm using the Menu Path Type "Default", but I have a German Drupal, so the Menu Path Type is "Standard". It is the only available Menu Path Type on my system.
In addition to my post i made last night: In Version 2.1 the "Item for Vocabulary", the menu entry for the "root" of the vocabulary, will not expand, instead the 404-error occurs.
Thanks for your help
Stefan
Comment #8
indytechcook commentedOk guys. It seems that an untested patch made it's way into the stable version. I was testing a patch from this issue and it made it into the stable commit. #408288: Add taxonomy items to any menu
Check out the newest stable and let me know. I apologize for the issues.
Comment #9
my-family commentedThank you, it works now! I would have only one question: is it necessary to list all terms on the top of the resulting page (= page with the whole vocabulary) and also all tid´s in URL? It seems to me not very transparent and user friendly, especially if there would be many terms in a vocabulary. I appreciated the "old way", which i know from older versions (especially D5, mabe older D6 versions too), better: only, e.g., "category/3" in the URL, and the name of the vocabulary on the resulting page. Would it not be possible? Thak you once more, Eva
Comment #10
Anonymous (not verified) commentedNow it works! Great!
Thanks again
Stefan
Comment #11
indytechcook commentedI'm glad this worked.
@my-family: Please see the documentation:
There is an feature request open for someone to create a patch for the page callback: #407490: Default Page Callback for Taxonomy Menu