How do i use taxonomy to generate listing for higher terms with number of child terms in bracket, with links to another page with the listing of the child terms, and so on

Comments

chasz’s picture

chasz commented

as a matter of fact how do i build a tree-menu for the hieracharcal taxomony??

michael_kirk’s picture

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

In 5.x, If you are doing a list/table view, add the taxonomy term as a field, and change the "default" value to be one of the summary options.
Does that work in 6.x?

michael_kirk’s picture

michael_kirk commented

What do you mean by a tree menu? Does it have anything to do with views, or is it something to take up with the menu/taxonomy people?

chasz’s picture

chasz commented

well well i thought i can automate it in Views rather than do manual listing with the Menus

i would like to do a directory listing, something like the yahoo directory listing with categories>>subcategories etc

Right now call i can do is

category
* terms
* terms etc

as an unheriachial list

michael_kirk’s picture

michael_kirk commented

Sorry for the lack of response, but I had an idea...
Have two views. One for the navigation, and one for the display of nodes within this category.

1. Create a view where the default is summary, as describe above. Enable the view as a block. Embed the block in one of the side panels, making it appear like a navigational entity. This view wouldnt display any nodes, but just be used to navigate and manipulate the url.
2. A second view, would list all nodes that fall under the categories described by the current url. (extract the info from the URL as an argument). This would require a bit of work, and using 2 views, but... to me it seems feasible. What do you think? If it's not clear what I mean, let me know. I could probably explain it more explicitly.

merlinofchaos’s picture

merlinofchaos commented

I just want to comment, I don't generally address hierarchy issues for Views. They're difficult in SQL, and Views doesn't handle it well. Often to do it right you need to make sure that you're storing extra data. For example, see the Taxonomy Lineage module (http://drupal.org/project/lineage) which stores extra taxonomy data so that Views can sort hierchically in a single query.

domesticat’s picture

domesticat commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

Closed while closing all Views support requests with no activity for 6 months. If you still need help, you may re-open this issue at any time.