Active
Project:
SiteMenu
Version:
4.6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
14 Apr 2005 at 17:30 UTC
Updated:
16 Apr 2005 at 20:05 UTC
I have a large organizational site in the works and it would be a very useful (or should I say crucial) feature to optionally not display every term for each vocabularly (particularly in the navigation block-- the sitemenu site-map page is fine with every term listed). However, when you want to simplify navigation for the user, it would be necessary for sites with large taxonomies (like my own) not to display every child term in the navigation block. I would love to see this flexibility implemented with sitemenu or site map (what are the key differences between these two modules, by the way?)
Comments
Comment #1
tostinni commentedAs far as I see, not so much :
- Site map got RSS feeds and can include navigation menu
- Sitemenu provide a block for site menu and a lot of comments with onmouseover funtion.
Btw I just write some littles suggestion here.
Comment #2
kbahey commentedI am not sure how this should be solved. I know that your ultimate goal is not to have a long menu on the sidebar for a site that has lots of terms. Do you want just the top level taxonomies and no children? Or a few of the children, then a 'More ..." link?
As it stands, it works best (as a side menu) for a limited number of terms.
I adapted this module from an existing one because I have a site with a lot of varied content from various areas of interest. People coming in via a Google search or other means may not realise that there are lots of other stuff that may interest them. I looked at taxonomy context, but it required lots of clicks to show the user the 3rd level or below. People get bored, specially on slow links or when they have to pay by the minute (outside North America for example). I also needed a site map that can be customized (terms only, or terms + nodes).
At present, it does what I want.
If you want to submit patches that preserves functionality the way it is, and adds new features via options (can be turned on and off), then I can include it in the module to expand its use.
I agree that there is a lot of overlap in various contrib modules of Drupal. This can be a duplication of effort at times, but eventually, the best modules are the ones that endure (if they are maintained).