I have just spent a week or so evaluating Drupal and find it to be a very mature, very comprehensive CMS.
I want to port a static html web site over to Drupal and I'd like to do it in such a way that moving forward I can take advantage of the features that Drupal provides. One of the things I have been struggling with is what to with its current static navigation menu.
I started by recreating that menu (list of single hyperlinks) using the core Drupal menu module. That works but I think as the site matures and I attract more viewers, and thereby over time more content, I'd probably want to go with the menu derived from a taxonomy.
I tried replicating the menu with the taxonomy_menu module. I defined each category with one of the list menu items from above, defining no terms for now. I did this because over time I expect the taxonomy to fill out and as this happens I could add the appropriate terms as necessary.
When I was all done I had my menu re-created but I had no way no associate a particular node with each item. Now I'm stuck.
Should I expect this to work, or is the only purpose of a category to provide a link to select that will expand and display its associated, selectable term item?
Thanks - Tod
Hi Tod,
I create a specific vocabulary for the menu (e.g., "Navigation" or "On this site") and then the top-level terms in that vocabulary become the top-level menu items (e.g., "About", "News", "Downloads"). As you've discovered, you cannot assign nodes to the vocabulary root, only to terms. In case you haven't look at it, the taxonomy_menu module will automatically build menus from specified vocabularies. It does, however, leave you with a top level "Navigation" link that
* Must be clicked before the user sees the category (term) links * Does not itself link to useful content, IMO (your choices are "Nothing assigned" message or a listing of every item assigned to every term in the vocabulary).
That said, it does automate the creation of a site menu system based on one or more vocabularies.
On Feb 27, 2006, at 8:39 PM, Tod Thomas wrote:
I have just spent a week or so evaluating Drupal and find it to be a very mature, very comprehensive CMS.
I want to port a static html web site over to Drupal and I'd like to do it in such a way that moving forward I can take advantage of the features that Drupal provides. One of the things I have been struggling with is what to with its current static navigation menu.
I started by recreating that menu (list of single hyperlinks) using the core Drupal menu module. That works but I think as the site matures and I attract more viewers, and thereby over time more content, I'd probably want to go with the menu derived from a taxonomy.
I tried replicating the menu with the taxonomy_menu module. I defined each category with one of the list menu items from above, defining no terms for now. I did this because over time I expect the taxonomy to fill out and as this happens I could add the appropriate terms as necessary.
When I was all done I had my menu re-created but I had no way no associate a particular node with each item. Now I'm stuck.
Should I expect this to work, or is the only purpose of a category to provide a link to select that will expand and display its associated, selectable term item?
Thanks - Tod
[ Drupal support list | http://lists.drupal.org/ ]
-- Ken
skype: thekenshow | msn: me@kendow.com
Not a shred of evidence exists in favor of the idea that life is serious. - Brendan Gill
Ken Dow wrote:
Hi Tod,
I create a specific vocabulary for the menu (e.g., "Navigation" or "On this site") and then the top-level terms in that vocabulary become the top-level menu items (e.g., "About", "News", "Downloads"). As you've discovered, you cannot assign nodes to the vocabulary root, only to terms. In case you haven't look at it, the taxonomy_menu module will automatically build menus from specified vocabularies. It does, however, leave you with a top level "Navigation" link that
- Must be clicked before the user sees the category (term) links
- Does not itself link to useful content, IMO (your choices are "Nothing
assigned" message or a listing of every item assigned to every term in the vocabulary).
That said, it does automate the creation of a site menu system based on one or more vocabularies.
That's exactly what I needed, thanks! Is there a way to get around not being able to link anything to the vocabulary root?
Tod
You could modify the taxonomy_menu module to have the top level link constructed so it points to something predictable location. For example, the module could always link top level to "/vocabularyname" and you could manually create a node at that path each vocabulary (using the menu module). Not perfect, by workable.
On Mar 1, 2006, at 8:47 PM, Tod Thomas wrote:
Ken Dow wrote:
Hi Tod, I create a specific vocabulary for the menu (e.g., "Navigation" or "On this site") and then the top-level terms in that vocabulary become the top-level menu items (e.g., "About", "News", "Downloads"). As you've discovered, you cannot assign nodes to the vocabulary root, only to terms. In case you haven't look at it, the taxonomy_menu module will automatically build menus from specified vocabularies. It does, however, leave you with a top level "Navigation" link that * Must be clicked before the user sees the category (term) links
- Does not itself link to useful content, IMO (your choices are
"Nothing assigned" message or a listing of every item assigned to every term in the vocabulary). That said, it does automate the creation of a site menu system based on one or more vocabularies.
That's exactly what I needed, thanks! Is there a way to get around not being able to link anything to the vocabulary root?
Tod
[ Drupal support list | http://lists.drupal.org/ ]
-- Ken
skype: thekenshow | msn: me@kendow.com
Too many people are thinking of security instead of opportunity. They seem more afraid of life than death. - James F. Byrnes
Ken Dow wrote:
You could modify the taxonomy_menu module to have the top level link constructed so it points to something predictable location. For example, the module could always link top level to "/vocabularyname" and you could manually create a node at that path each vocabulary (using the menu module). Not perfect, by workable.
What I ended up doing is making my welcome page the default page, made the first menu item under the navigation menu headerpoint to it, and then made it sticky. That seemed to accomplish what I needed.
- Thanks
On Mar 1, 2006, at 8:47 PM, Tod Thomas wrote:
Ken Dow wrote:
Hi Tod, I create a specific vocabulary for the menu (e.g., "Navigation" or "On this site") and then the top-level terms in that vocabulary become the top-level menu items (e.g., "About", "News", "Downloads"). As you've discovered, you cannot assign nodes to the vocabulary root, only to terms. In case you haven't look at it, the taxonomy_menu module will automatically build menus from specified vocabularies. It does, however, leave you with a top level "Navigation" link that * Must be clicked before the user sees the category (term) links
- Does not itself link to useful content, IMO (your choices are
"Nothing assigned" message or a listing of every item assigned to every term in the vocabulary). That said, it does automate the creation of a site menu system based on one or more vocabularies.
That's exactly what I needed, thanks! Is there a way to get around not being able to link anything to the vocabulary root?
Tod
[ Drupal support list | http://lists.drupal.org/ ]
-- Ken
skype: thekenshow | msn: me@kendow.com mailto:me@kendow.com
Too many people are thinking of security instead of opportunity. They seem more afraid of life than death.
- James F. Byrnes
-
Ken Dow -
Tod Thomas