This instruction is only valid for MENU PATH TYPE: HIERARCHY!

The vocabulary might be like:
Vocabulary
Term-1
-- Term-1.1
-- --Term-1.1.1
-- --Term-1.1.2
-- Term-1.2
Term-2
-- Term-2.1

What is needed:
Modules TAXONOMY MENU with TAXONOMY MENU HIERARCHY and VIEWS

That´s the way:
- Create a view with a path: category/% (where the term "category" can be chosen)
- Add fields and filters according your needs
- Add the following arguments:
Vocabulary ID (Title: %1)
Term ID (Title: %2)
Term ID (Title: %3)
Term ID (Title: %4)

Got to admin/content/taxonomy
- Select the vocabulary you want to have a menu for.
- Select "Menu:" (where the menu should show up)
- Select "Menu Path Type: Hierarchy"
- Enter "Base Path for Hierarchy Path: category" (or what you have chosen as path for view)
- Optional: Display Number of Nodes / Auto Expand Menu Item
- Check "Item for vocabulary"
- Do NOT check "display descendants"

After saving the menu should appear.
Now comes the BUT: most probably you don´t see any nodes when klicking the menu items.
For Term-1 the path is: ..category/vid/tid, for Term-1.1.1 it is category/vid/tid/tid/tid
Everything behind "category" will be taken as arguments in views.
So only those nodes will be shown that are linked to the taxonomy terms Term-1 AND Term-1.1 AND Term1.1.1. within the vocabulary (it is a logical AND function, whereas multiple arguments TermID TermID TermID is a logical OR function).
Once you have linked your nodes to the taxonomy terms in the described way, they will be shown when klicking on the menu items. It produces nice breadcrumbs and page titles (remember to set the titles for the arguments in views as described) - and it allways display descendants.

Unfortunately (as far I can see) there is no function or widget neither in core TAXONOMY nor in CONTENT TAXONOMY module that supports this functionality, like: "only lowest hierarchy level selectable" and "parental items automatically get selected".

[Neil, should this explanation be integrated in the readme.txt?]

CommentFileSizeAuthor
#8 README.txt10.62 KBksc
#4 README.txt10.07 KBksc
#3 README.txt9.87 KBksc

Comments

indytechcook’s picture

Status: Closed (works as designed) » Needs review

Yes it should be. This is great. I'm changing the status to "needs review" and treating this like patch to the readme ;)

ksc’s picture

Please also see http://drupal.org/node/399380

and [Neil, I´ll revise the readme.txt - you just need to check my English afterwards]

ksc’s picture

StatusFileSize
new9.87 KB

Hi Neil,
attached is a revised README.txt
I restructured it a bit and add several explanations.

Could you
1) check my English
2) check the paragraph about integration with other modules esp. i118, Pathauto and Domain Acess.
3) Are there any new options or functions in the latest dev? I haven´t installed that yet.

:-) Klaus

ksc’s picture

StatusFileSize
new10.07 KB

UPPS:
I forgot an important detail.
So here is a corrected version.

indytechcook’s picture

no new features totally working yet. i18n is close. there is an issue with "item for vocabulary" setting.

what do you think of these patches:
http://drupal.org/node/424160
http://drupal.org/node/424160
http://drupal.org/node/408288#comment-1380600

they work and I was thinking of adding them. Not sure though.

ksc’s picture

(two links point to the same node)
These options seem to make sense but I think it is better not to add new functions to the current version.
Let´s just clean it from bugs - it is already so much better than the 6.x-1.0.
The patches might look ok but you have seen how easy incompatibilities with other modules happen.

Why not start with the 6.X-3.0 dev - many people are waiting for possbility, to have more that one Menu Group for a vocabulary or to just have certain terms from a vocabulary within a menu - me included.

I suggest to start with a version that can link one vocabulary or parts of it to a Menu Group. It could implement the functions you refer to and other stuff we discussed under "Basic consid..."

The possibility to add terms from more than one vocabulary could come in a later version - this might be the heaviest part because it has some logical pitfalls.

ksc’s picture

I wrote in my issue (and also in the README.txt):

Unfortunately (as far I can see) there is no function or widget neither in core TAXONOMY nor in CONTENT TAXONOMY module that supports this functionality, like: "only lowest hierarchy level selectable" and "parental items automatically get selected".

I just found a module that seems to do that: http://drupal.org/project/hierarchical_select
Neil, do you know that module?

ksc’s picture

StatusFileSize
new10.62 KB

I checked the module Hierarchical Select to link taxonomy terms to a node.

For using "MENU PATH TYPE: HIERARCHY" within Taxonomy Menu the HS options "Save term lineage"
and "Force the user to choose a term from a deepest level" should be enabled.

(I´ll) I have updated the README.txt for Taxonomy Menu and included this info.

:-) Klaus

indytechcook’s picture

Version: 6.x-2.3 » 6.x-2.x-dev
Status: Needs review » Fixed

readme has bee updated in the latest DEV. I made a few small modifications.

Status: Fixed » Closed (fixed)

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