Seeking some advise.
I am Currently using D6 and Taxonomy Menu to set up the category navigation.
Please see the following site DayofTheDead.com
The root vocabulary (blog topics) contains many terms.
The main navigation menu item (blog topics) links to the root vocabulary. When clicked, it displays the page with a header listing all terms under the vocabulary in alphabetical order followed by the list of nodes in teaser form.
The sidebar block displays the Taxonomy Menu as expected.
Here are my questions:
How can I suppress the comma separated list of therms from the page when rendering the vocabulary root? I would like the page to display only the vocabulary root term as the heading for the page. Do I need to create a separate view for this? If so, do I need to create a separate tpl file that handles the vocabulary ID? How do I get the taxonomy menu block to display the active items.
In the case of navigating to Blog topics > Regional Traditions, as an example.(this applies to all nested terms)
How do I get it to display the term parent only in the header portion of the node list?
Can Taxonomy Menu create a short URL for the vocabulary root? currently it shows as taxonomy/term/tid tid tid tid etc, etc instead of /vocabulary root. The same happens for any parent of any nested group.
example here: blog topics > regional traditions Note the term/tid tid tid format.
However if you click one level down it reverts to a friendly URL as in blog topics > regional traditions >Day of the Dead in Mexico City with a friendly format of category/vocabulary root/nested parent/term
I appreciate any comments and/or suggestions. I have been searching all over, tested various modules without any luck.
Thanks in advance, and I apologize if I am posting this in the wrong place.
Sandro.
Comments
Comment #1
indytechcook commentedSandro,
I want you to know that I'm not ignoring you. It's just not a simple answer and I don't want to give you a half response.
Comment #2
TamboWeb commentedHi Neil,
Thanks for the reply. I know this is a special request for a very specific application. I am currently doing some tests that may help me narrow down the scope.
So far I have been developing sites with Drupal by integrating themes and modules. I think now has come the time for me to get involved/familiar with the API to really reap the benefits of Drupal.
The Taxonomy menu module is the best solution for my application. I will keep posting here with any new info.
Thanks again for taking a look at my issue. Look forward to any input.
Sandro.
Comment #3
TamboWeb commentedHere is an update;
I just realized that this is NOT an issue with the Taxonomy Menu at all. Instead I think it is an issue dealing with how to customize the taxonomy view. So far the taxonomy menu is doing what it is supposed to do.
In my setup I have the "Taxonomy Menu Module" working in conjunction with the "Menu Block Module", I also tried the "Taxonomy Title Module" but got mixed results with multiple tid artguments.
On a separate note; I also noticed that If I set the Taxonomy Menu Module to use the "All" argument at the end of the URL, the Menu Block disappears (not a desired outcome). Not sure why, but I think it may have something to do with the URLs.
I will also experiment with the "Taxonomy Redirect Module" and custom views to see if I can get the desired results for the views page.
A pending issue that still remains for my application is how to customize the views page title. I am not sure if handling my original issue with custom views would resolve my problem or will it create a bigger site management task. I am not sure if this approach would then require that a custom view be implemented for each menu item.
I think if I find a solution would make a good write up for the drupal community. So far the Taxonomy Menu and Menu Block modules provide an excellent way to navigate the site.
Will report again soon.
Sandro.
Comment #4
indytechcook commentedSandro,
You pointed out one of the reasons why it's hard to answer. It is the combination of the link path and menu callback that causes lots of confusion. It's very difficult for me to explain how the menu system works to non developers. There are so many different options (love Drupal) that everything I say doesn't work for everyone.
The write up (recipe) is exactly what we need more of. There are a few in the readme but there are so many different options, it's hard to catch them all.
Comment #5
TamboWeb commentedI almost got it to work.
First, thanks for your comments. I know that there are more than one way to do things here in Drupal. I am also being realistic about the fact that each implementation is different and possibly unique. Please note that I am not implying that there is anything wrong with the module. On the other hand, I am very pleased with what it does.
OK... Here is what I got going;
I created an new template file "page-taxonomy.php.tpl" since I am only using one vocabulary so far. I commented out the "print $title" statement for the interim. Now I get my pages without the long list of terms on the page H1 title tag.
Now to get it to work I would need to grab the variables used to build the block menu. Specifically, it would be great If I can target the active "Menu Item" and pass it to the "page-taxomomy.php.tpl" file. If I can figure out how to substitute/replace the title string with the "menu item", then the taxonomy page will have the same title as the menu link.
I'am currently researching the themeing documentation to see if/how I can implement this. I am some what confused about preprocess functions and such. If I am going in the wrong direction, please do tell.
Thanks.
Comment #6
dstolOld issue closing