Taxonomy_menu

By dima-1 on 13 May 2005 at 15:30 UTC

Hi,

How does one publish content in taxonomy_menu root ?
It does not allow me to select root, only the term in the vocabulary.

Thanks in advance.

Comments

Node are not associated to vocabulary

tostinni commented 13 May 2005 at 16:00

I think it's a common mistake, which is not well explained in taxonomy help.
Vocabulary are the global name for you category (ie terms) tree. So you can't put a node under a vocab, it should have a term being associated or nothing (it's what happens when you select none under a vocab when a term is not required).
So if you create vocab News, you would create the term "General News" to hold all content that won't fit the other terms ("political news", "economical news" and so on...)
See a little comment I made a few weeks ago
http://drupal.org/node/20261#comment-27402

This is exactly the question

venkat-rk commented 13 May 2005 at 17:00

This is exactly the question bothering me for the last several months. All terms have pages, but a vocabulary has no index page.

One can do a workaround by mapping a url alias (taxonomy/term/1,2,3) to a page that gets all nodes from the terms of a vocabulary, but I am not sure if this is a good enough workaround. Also, it produces a page title that lists the names of the terms separated by commas (Term 1, Term 2, Term 3) and not the name of the vocabulary, as it ideally should.

Here again, one can use the locale module to change the title to the vocabulary name, but all this seems a hack. Any comments?

Create "root term"

tostinni commented 13 May 2005 at 17:50

As I mention up, in this case, I'd prefer create a "root" term that may have the same name as vocabulary and it makes what I want.
So if you want to see all term from a page, well, I prefer using taxonomy_menu module and allow "Display descendants", then I would browse to my "root term" and get all terms from my taxonomy.

Soultion for my site

bomarmonk commented 13 May 2005 at 18:41

In my case, I used the new node-list module along with the book module (I will use multiple nodelist modules--hacked to be nodelist1, nodelist2, for each vocab). Then I enable nodelist only with books, so I get an index for each vocab based on the root of each book.

A bit weird, but it delivers the results I wanted for the website I'm working on. If you wanted to do the same thing with other nodes, pages-- whatever, you should be able to achieve similar results.

Thanks, but I find it a

venkat-rk commented 14 May 2005 at 05:28

Thanks, but I find it a little hard to understand- about the root term. Could you please explain to me step by step, if you have the time?

i'm pretty sure

green monkey commented 14 May 2005 at 05:34

i'm pretty sure he means

-Create your Vocab "apples"

- Create your 1st term under vocab "apples" and cal it "apples" too

- then your remaining terms are created under the TERM "apples" and not under the Vocab "apples"

(well actually it is under your Vocab "apples" - but not directly)

This is a nice approach and

venkat-rk commented 26 May 2005 at 10:49

This is a nice approach and does have its advantages. The only problem is that I have to choose only the root term (not the child terms), or it doesn't work. This means that:

1.) It displays the same word both in the page title and the link to the term.
Example: www.actfordharma.org/development/campaigns

2.) It doesn't give me the opportunity of linking to the other terms, which is possible if the alias I create for this page is based on taxonomy/term/x+y+z
Example: www.actfordharma.org/development/kanchifacts

The downside of No.2 above is that it prints out the term names separated by commas as the page title, instead of just the vocabulary name

Is there a simple way to get this page to display just the vocabulary name in the title instead of the terms? This may solve my problem.

The problem remain the same,

tostinni commented 26 May 2005 at 15:04

The problem remain the same, you can't see a vocabulary, because no nodes are attached to a vocab, but to terms.

Also when you will try to build taxonomy/term/x+y+z menu (can be custom to override limitation of taxonomy_menu), you will always see list of terms separated by coma, because there's no easy way (for taxonomy module) to know if all selected terms include the whole vocab term...

So the "root term" solution I gave upward appeers to me as the only solution...

you can't see a vocabulary,

venkat-rk commented 27 May 2005 at 05:05

you can't see a vocabulary, because no nodes are attached to a vocab, but to terms.

Just to be clear. Is it *impossible*, technically, to do this in Drupal or just that it is not currently implemented?

If the latter, I am thinking of paying a small amount to some developer to implement this feature. While I like the idea of using book pages with node list module to build a hierarchical site structure, I am a little more comfortable with my approach.

There is also a new hierarchical module available that is very interesting. Has anyone looked at it?
http://drupal.org/node/23055#comment-39667

The problem with this

adub commented 13 October 2005 at 16:38

The problem with this approach is that a new node can then be submitted to the root term when you may want only the children to be selectable.

This was the idea of the

tostinni commented 13 October 2005 at 16:43

This was the idea of the first post, that's why I came with this solution ;)

It's all fine BUT....

dima-1 commented 15 May 2005 at 10:46

It's all fine, but the "root" option creates unnecessary branch in hierarchy, thus cluttering the looks of your navigation and forcing onto user an extra click, which you know is not advisable for a professional site.
Any ideas to workaround this one?

Ah, clarification

bomarmonk commented 15 May 2005 at 17:12

The node-lists/indexes for each taxonomy term (that I want an index for) are built using the node-type book. When I create additional book pages, I make sure that these pages are "pages," "webforms," "flexinodes," etc.. This way only the parent-root of the book is indexed.

I'm not suggesting that this is a solution for everyone, but it will work for my site. Instead of using taxonomy_menu, though, I'm building custom menu links to the node-lists and parent-book pages.

Not sure

RobRoy commented 6 June 2005 at 18:29

I'm not sure if I get this...having the same problem. So...

There is no module that will let you browse a vocab like /vocab/4? It shouldn't be too difficult to write a module to do so right?

I have a links vocab along with tons of unrelated vocabs, so I want a "links page" and feel I should just be able to browse the vocab to see all the terms, subterms, etc.

Would someone please advise? I was going to just create a main term with the same name, as stated above, but feel that a vocab browser should be easy to do.

There used to be a

venkat-rk commented 7 June 2005 at 05:37

There used to be a 'weblinks' module (now called directory, I think), but I honestly don't know if it displays the vocab pages.

Someone mentioned in another post that the taxonomy_menu module gives them a vocabulary index page, but, by default, this vocabulary menu shows in the navigation. I would like to move the menu for a vocab into its own block outside the navigation, but, if this is okay with you, you could try out taxonomy_menu module.

Hope this helps.

There is a weblinks module

sepeck commented 7 June 2005 at 05:59

There is a weblinks module still there, just rewriten. Now, you add the directories module to build a heirechy of links. The directory module is available in cvs.

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
_{Drupal Best Practices Guide}

taxonomy_menu mod to make a term the top level of the menu entry

peterx commented 29 November 2005 at 10:33

taxonomy_menu mod to make a term the top level of the menu entry:
http://drupal.org/node/39125

petermoulding.com/web_architect