Category_menu features

Category_menu is a module that is included as part of the categoryi package. It creates and manages a set of menu items that correspond to your site's category hierarchyi. Features include:

Creates database menu items
Drupal has two types of menu items: those that are defined by modules in code; and those that are defined by users in the database. Category_menu is the first module ever (as far as I know) that breaks this convention, and that defines menu items directly in the database, rather than in its code. This approach is so unique that Drupal doesn't even have a mechanism for supporting it: that is, it didn't, until an interface was developed especially for category_menu. Using database menu items brings with it many advantages: the menu items can be arranged hierarchically; they take precedence over those defined in code; they are accurately reflected in a site's breadcrumbs; they can be displayed automatically as a block; and they can be edited and even re-structured by the end user, through the administration interface in the menu module.
Responds to insert, update, and delete
Every time that any of these three operations is performed on a category or containeri, category_menu has complex and intelligent logic that governs how it will respond. No matter what you do with the structure of your categories and containers, category_menu will match it in the menu hierarchy.
Intelligently updates child menu items
The category module supports multiple parentis for each category or container; but the menu system allows each menu item to have only one parent. This presents a dilemna for category_menu, which is solved by always treating the parent of lightest weighti as the 'primary parenti'. It also means that when a category or container is updated, all of its children with multiple parents must also have their menu items updated. Yep, we really do have all bases covered.
Can manage assigned nodeis
You can configure category_menu to create menu items for assigned nodes as well, on a per-container basis. The same intelligent update logic is applied for assigned nodes that are tagged with more than one category, as is applied for categories or containers with more than one parent.
User-defined root menu
Don't want your menu items being generated under the standard 'Navigation' root menu? You can easily re-configure category_menu to use a different root menu, such as one that you created yourself using the menu module.
Handles distant parentis seamlessly
No matter how complex your distant parent structures are, category_menu can handle them. Categories or containers with any number of distant parents are handled with the same intelligence as those without.
Elegant hidden containeri handling
You can set a container to be 'hidden', and category_menu will neglect to create a menu item for it. Not only that, but children of this hidden container will have menu items generated, and their parent will be the parent of the hidden container, effectively 'skipping over' the hidden container in between! This way, users of your site don't even need to know that your hidden containers exist - they're simply not there in the menu hierarchy.
Doesn't break when you mess around
Within certain limits, you can re-arrange the menu items generated by category_menu, using the administration interface in the menu module. For example, you can set a root-level container to be the parent of the 'events' page on your site.

but how???

this sounds like it would be VERY useful... does this mean i can automatically get a menu based on outline of a containeri or of a set of categories. This would be great... if only i could figure out how to use this...

what is this module supposed to do?? Do i get a block that i can turn on? Do i get automatic menu items generated and i need to go and assign them to a block? As it is i have spent many hours trying to figure out how to get menus out of categories and i have given up and them come back to it for other sites where i again needed to get it working...

maybe just a small clue as to how one would use this?

thanks,
peter...

Menu blocks

Category_menu generates menu items, which are virtually equivalent to the menu items that you can create manually on your site's administer -> menus page. The idea is that categoryi_menu only handles the menu items themselves, and that the core Drupal menu module handles everything else (e.g. block display, manual editing of menu items).

Like custom menu items, the menu items that it generates can be viewed and edited on the administer -> menus page. And like custom menu items, the menu in which the items are generated has a corresponding block, which can be enabled on the administer -> blocks page of your site. The menu in which the items are generated defaults to the Navigation menu, but this can be changed on the administer -> settings -> category page.

Can a container be searched

I have built a site using cck to create a page type this has many terms associated with it. But I have been surprised to discover that in actual fact the terms are not actually searchable using the built in search module.

If I import these vocabs into containeris and categories will these be searchable as they are actually nodes ?

I have written a template to display the page how will this need to be converted to work with the categoryi menu system ?

If you can give me some pointers as to what I'll need to do I'll happily write up the conversion process as a newbie to drupal and even newer newbie to the category module !!

If you want to look at my existing test site you can see an example page

here http://cms.dibbletree.com/node/85

to make my terms searchable I have as a test created another node with the body content equal to the actual term name and then added the relevant tags to it

an example of the only test one is here http://cms.dibbletree.com/node/90

I have to admit I dont fancy progressing in that fashion as there could be several thousand names eventually

I posted about this on drupal and someone suggested the tagnode module which when I checked it out, it in turn pointed me to here !!

So are categories searchable !!

thanks in advance

Tkgafs

why is the date wrong on my post above

I posted the mesage above yesterday 15th April 2006 yet the date is set to 1st January 1970 !!!

any idea why

Site problem

The date on your comment got set wrongly because of a bug in Drupal core that was affecting the site. The site has just been upgraded to Drupal 4.7 RC3, and the problem appears to be fixed (I had to manually fix up the date on affected comments, though). All should be well now.

menu module

my main problem is the shear size of my menu; i have 2000 nodes on my website in a pretty simple hierarchyi using the current 4.75 build - almost all of which have menu items.

of course this means that performing administration on the site, specifically the menu is very slow and cumbersome. does the categoryi module still create these menu lists as the old setup does?

i would prefer some kind of menu system where you could limit the admin/menu screen to just containeri objects, with the child menu items populating themselves based on their node/category hierarchy, is this possible?

an added bonus would be integration with the weblinks modules and the wysiwyg content editors to allow menu links to be chosen via a hierarchy.