Posted by btbroot on March 19, 2009 at 6:27pm
5 followers
Jump to:
| Project: | Taxonomy menu |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
This seems odd to me to get a taxonomy/term/$tid1 $tid2 $tid3 ... page as a vocabulary content page which is titled as $tid1 $tid2 $tid3 .... Just imagine a vocabulary with 1000 terms...
This is obviously a usability bug! The vocabulary page should consist of same data as in Navigation menus, as it was in 5.x, and it should be titled by the vocabulary's name.
Comments
#1
Thank you for using Taxonomy Menu.
As of version 6.x-2, Taxonomy Menu no longer handles any of the page call backs. It only creates the menu links (title and URL). Everything displayed on the page (include the title) is control by what every module is displaying the information. If you are not using a view then the taxonomy module handles the display and title for the default path.
Do you have a better suggestion for the path to use for a vocabulary item?
You have a few options. You can either use a view or write a custom module.
If you use a view, be sure to read the README.txt for information. There are also instructions on several other issues.
If you wish to program your own path or page call back see here
Thanks,
Neil
#2
Thanks for suggestion and my pardon for the duplicate!
#3
Changing this issue to a feature request to override the default taxonomy module page callback.
If someone would come up with a patch, I would be willing to review to add to the main module.
#4
It would be great if there is an option to turn off the display of descendants in the title when the option "display descendants" is enabled.
If there are many descendant terms, the title gets too long. Only the parent term should be shown in the title.
#5
Quick fix for changing the root page to taxonomy/vocabulary/<$vid>. Then using Taxonomy List module you're up to speed again.
Taxonomy_menu.module line 533 function.
Change the $path line. Be happy.
function taxonomy_menu_path_default($vid, $tid) {//if tid = 0 then we are creating the vocab menu item format will be taxonomy/term/$tid+$tid+$tid....
if ($tid == 0) {
//get all of the terms for the vocab
$vtids = _taxonomy_menu_get_terms($vid);
$end = implode(' ', $vtids);
$path = "taxonomy/vocabulary/$vid";
}
Cheers
Alex
#6
Alex, I like it but it doesn't work with Core. You would need views or another module to control the page callback.
Good idea though. It should help others get a site setup.
I recommend that you create a new path rather then use the default. Instructions can be found here: http://drupal.org/node/380652
Cheers
#7
Sorry, Dup comment!!
#8
Neil,
I'd like to add my vote for this feature request as well. The problem manifests itself in 2 different areas. First, the vocabulary content pages get the unwieldy taxonomy/term/$tid1 $tid2 $tid3 ...URL. This can't be addressed by Pathauto to turn it into something more SEO friendly. Second, the Page Title comes out as $tid1+$tid2+$tid3 ..., which is impossible if you have more than just a few terms.
If the feature to override the default callback could be used to allow the menu to call 2 different Views, that would solve both problems. You could create one Vocabulary Term View for parent terms, and then use the default Taxonomy Term View for children. It could then be up to each user to decide whether the Vocabulary View page would show all children nodes, or just a list of links to children terms.
Thanks for your consideration.
#9
A sudo patch was submitted that may help here. If someone would turn this into a patch that adds a new menu path type then it would be easy to commit.
#424160: Module for adding a custom path for the vocabulary only inserts garbage chars (%252F) before the vocab name.
#10
There is also a patch in being worked on here: #356281: Custom menu titles
#11
Adding request to set the taxonomy term on node page from this feature request: #511460: Menu colapses when in the node body
I'm making it pare of this request because it deals with the page display.