from what i understand.. (and at first the main reason i didn't use cat_menu module) is that it seems to put menu items for all the categories i added into the navigation menu... thus very quickly cluttering it up to the point of being useless.

now that i know the cat module a little better i see a couple ways around this:

1. turn off making menu items for that container
2. set default MODULE dumping menu to something else
3. disable cat_menu module

but.. if i have all the above correct so far.. why wouldn't the default menu be on a container by container basis.. so that all cat based menu items that get created go where you want???

This seems so natural to me that every time i am away from this and come back not remembering why cat_menu module is making such a mess of things.. i always first go looking in admin/category thinking i can set the menu default there.. and then eventually realize that for some odd reason it is a module specific thing.

Am i missing something here?

Peter Lindstrom
LiquidCMS - Content Management Solution Experts

Comments

stefgosselin’s picture

stefgosselin commented

I am really digging down in all the docs I can find on the category module. It is well documented but still a little vague.
They way I understand it is you can select the options to hide menu items, as you stated, and also to create hidden containers.

venkat-rk’s picture

venkat-rk commented

why wouldn't the default menu be on a container by container basis.. so that all cat based menu items that get created go where you want???

One way to override category items getting dumped into the default navigation menu is to manually create a menu at ..admin/menu (not sure what the path is in 5.0) and have it as the parent of the container which has the category items. The rest is just enabling this menu block at ../admin/block. This makes it easy to have separate menus for each container.

Hope I got your question right.

liquidcms’s picture

liquidcms commented

sorry.. either i am missing both the answers hear or my inital post was not that clear.

re: #2 - yes, i can set up another menu (block) and assign that as the SYSTEM WIDE default menu for the cat_menu module to dump items into... BUT... as far as i can tell i will now get EVERY menu item created by the module in that block.. as i mentioned above.. this is mildly better than the default of having all the items go into the Navigation menu...

BUT... what i was asking about or suggesting... was why can i not set a default menu for each container.. this way if i had categories to container X they go into menu (block) X and if i had items to container Y they go into menu Y.

Hope this helps...

jstoller’s picture

jstoller
he/him
commented
Version: 4.7.x-1.x-dev » 5.x-1.1

I am having this same problem and it is driving me crazy! I created a container for Primary Links and a container for Secondary Links, but I can't figure out a way to properly generate these two menus.

JirkaRybka’s picture

JirkaRybka commented
Version: 5.x-1.1 » 6.x-2.0-rc1
Status: Active » Fixed

As of 6.x, category_menu is a bit different beast, and you're quite able to choose the menus per-container there. So I see this as fixed for 6.x.

As of 5.x - unfortunately, it's not really a maintained version now, so a backport of the fix is highly unlikely, also because there's a big difference in both category_menu and the underlying core menu system, between 5.x and 6.x. Anyway, the lifetime of D5 is slowly nearing its end now, so I guess not much people are going to adopt the 5.x version now, who didn't solve the problem somehow already.

Feel free to re-open, if needed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.