Closed (fixed)
Project:
Taxonomy Menu
Version:
6.x-2.9
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
27 Apr 2010 at 23:34 UTC
Updated:
24 Dec 2013 at 22:50 UTC
Jump to comment: Most recent
Comments
Comment #1
mb2449 commentedI am actually having the same problem.... I am working on this now....
Comment #2
mb2449 commentedI switched back to default, now I dont get anything.
Comment #3
mb2449 commentedOk, I figured it out. If you messed with the default taxonomy page path with views, reset it.
Comment #4
TimG1 commentedIt's working for me. I didn't have a View in place which is why it wasn't working. Didn't read the fine print under the "Base Path for Custom Path field".
"You need to have a view with path 'custom path/%' and an argument 'Term ID' before you create this taxonomy menu."
Thanks!
-Tim
Comment #5
dexter971 commentedI have the same problem ! solution ?
Comment #6
bloyo commentedSame problem here. I have created view with path = category/% .It has
Argument = Taxonomy - Term Id
Validator options
Validator = Taxonomy Term
Argument type: Term name converted to Term ID
Still doesn't show items in menu which i choose in Taxonomy Vocabolary Settings.
Comment #7
summit commentedSame for me also.
Have view with category etc... For another site I have this working, but with new site no go. Trying for days now..
I set view underneath, so you can test it, NO taxonomy menu items are shown? What could be wrong please?
Comment #8
summit commentedHi,
I have something working, only using hierarchy, instead of custom path.
What I had to do was to clear the cache, to get the menu pop-up!
You have to do this every time after renewing the taxonomy menu within the taxonomy.
greetings, Martijn
Comment #9
indytechcook commented@Summit, sounds like a block/page level caching issue.
To others, make sure you read the readme.txt for information on configuring the view and taxonomy menu path. The number of arguments in the view has to match the max number of tids you could have.
There are a large number of configuration options. There is no one single answer to this question. If the path in taxonomy menu does not have a menu router path to match against (like a view path) then the menu will not be created. This is not a feature of taxonomy menu but how drupal core works. I've been trying to figure out a better way to handle this.
Comment #10
bloyo commentedthank you ... i just needed to read README.txt :)
I was putting in full path = category/% . You just need to add category path = category.
Thank you again ... nice module
Comment #11
webgears commentedWhat base path do i have to enter if the term-id is between other arguments?
My example is: nodetype/%/hot
Comment #12
chunty commentedAfter hitting this issue myself, reading various things on this and some educated guessing I found something that might help a few people:
1) As the readme suggests you do need a view in place to match your custom path before you try to tell your taxonomy to create a menu and you DON'T have to have "Allow multiple terms per argument" ticked
2) ...but it doesn't end there - the other really really important bit is what you're doing with your validation and what you're doing if the argument is not there! - If in either scenario (argument missing or argument does not validate) you are returning a 404 then taxonomy menu will NOT create the menu.
I didn't have anything to do with the creation of this module so I can't be certain but the note about the view needing to exist led me to second guess that what's happening behind the scenes when you press save is that a call to the view is being done to validate its existence of the view. So let's say your view should normally be called in form http://yourdomainname.com/viewname/termID then all that gets called is http://yourdomainname.com/viewname thus if your validation of arguments (or behaviour of what happens when there is no argument) results in that returning a 404 that's the same as the view not existing so it decides not to create a menu.
Personally I think this is wrong because actually my view does exist and the menu will always pass an argument so to have the validation in place is correct however I leave it to the module creator to comment on this....and maybe its a bit cheeky but I've put the status of this back to "needs review"
I had hoped once the menu was created I could change the settings on my view back but it seems if I add another term then that kills the menu..
Incidentally although this issue is for 2.7 I'm actually on 2.9 and it'a still an issue.
Comment #13
chunty commentedBit of an update on this after further playing...
It seems the critical issue is the validation and NOT what to do if the argument is not present. If this is set to give a page not found then the menu's page for the specific menu at admin/build/menu will not show a menu, however either empty text or display all values works fine
Further more it seems that although drupal will not show the menu the menu does exist but as posted in #9 for some reason the drupal menu system decides that it won't show any of the items but if you look in your database they are actually there.
Grrr
Comment #14
kappaluppa commentedThis is how I got custom path to work. It took a while and I kept breaking it. But finally got it to work. Although you don't have to use Menu Block to set the menu I did so that I can have multiple menus with multiple views. I hope this helps someone! (and with it here I can refer back to it if I break it again! lol)
Created view with arg, settings as follows (some settings may not be needed by you):
View Page display Path setting:
category/%1
Arg settings:
Taxonomy Term (not ID. I set "use term name" in the vocab settings)
Title: %1
Basic validation, Hide view/Page not found
Case: Capitalize each word
Enable Transform spaces to dashes in URL
(that's it - did not use allow multiple args to work together because was causing "Reduce duplicates" setting not to work)
Vocab settings:
Menu path type: Custom path
Custom path for vocabulary: blank
Base path for hierarchy path: blank
Use vocabulary path as base path: deselected
(I only mention the above because I think they are populated by default)
Base path for custom path: category (no /% as in the view path setting)
Use Term Name: selected
Display number of items: selected
Hide empty terms: selected
Auto expand menu times: selected
You can see it in action here: http://marketplacedirectoryonline.com/ (I'll try to remember remove this link if the site changes and it no longer applies.)
I have one problem left on this baby... The count adds 1 more than is there... but that is for another thread
Find me in IRC if you have any questions... I'll try to help!
K
Comment #15
dstolComment #16
yixia commentedMenu path type: Custom path
At first, I set Base path for custom path: products/%(I have a view with argument termid, its path is products), no menu items showen, but I have seen someone upper said the menu items exists in menu_links table, and I checked, that's right.
Just change the path to "products" , remove the "/%" from the path, it works.
Comment #17
dstol