Customize the Add Menu Path Requirement

By bendshead on 9 Dec 2008 at 14:08 UTC

I'm looking for a solution to prevent a parent item in a menu from having to actually be a link. I would like to use the parent item as a "category" in an expanded menu, but not have any content specifically for the parent.

You'll notice that when adding a menu item, a path is required -- thereby forcing you to create a link from the menu item to a node. My "wish" (as a matter of convenience) would be that the path was not required. Then I could create a menu item that would not link to anything but my menu functionality behaves as expected (when you scroll over the parent item, the child items appear and are linkable). But I would also entertain a solution that makes all parent item non-linkable (indeed, serving as menu categories).

For example, say I have articles about Big Boats, Red Boats, Fishing boats

I would like them all to fall under a "Boats" section in the menu but do not have content for the parent item "Boats". I could add a page for "Boats" that simply contains links to the child items but I would prefer not to. I want to be able to hover Boats and see the child items.

I would like to continue using my Roople Lite Jazz Theme with Suckerfish Menu.

My strong preference is for a solution via module. I would be willing to release this solution to the community upon completion.

Please contact for further questions and request for examples.

Comments

you could try

vivianspencer commented 9 December 2008 at 14:30

you could try http://drupal.org/project/dhtml_menu and see if it works for you, although it might not be exactly what you're looking for

There's are demo here: http://dev.ermarian.net/dhtml_menu/

There's also a big discussion on this topic here: http://drupal.org/node/128618

- Vivian

...an issue with a past

bendshead commented 10 December 2008 at 06:30

Viv, Thanks for pointing that rich discussion of what others, as well, perceive to be one of those simple features that may have been overlooked in the scheme of all the other amazingly powerful things Drupal can do. Interesting to note, as well, that after more than two hours researching this issue, I never came across the thread you pointed. So my promise going forward is to make sure this solution gets document the best way possible as to be accessible to most possible users.

The DHTML Menu module can nearly do what I am after: create a menu item that is essentially a placeholder, but when clicked can expand its child menu items. The only problem is that it does not play nice with Suckerfish.

I would still be interested in seeing if a module can be written to handle this requirement -- what may be as simple as being able to optionally add a null value to a menu item (for example: a href="#") -- so in this way, any CSS menu can have this functionality, not just with the DHTML mod.

If the price is right, I would like to see if this module can be written in the interest of satisfying not only my need but a need in the community as well. Again, see http://drupal.org/node/128618 if you don't believe. : )

Here is an additional thread to provide some reference to what I'm trying to do:
http://drupal.org/node/274632

Thanks, all!

Strange that this isnt

Marko B commented 18 March 2009 at 20:03

Strange that this isnt possible so far, that its not in core also as its very common feature needed in web page building. I would say its even more logicall to use it as container then as actuall menu.
Currenlty i have access permission problem with this, as if i have conatainer menu point to some path it looks for permissions and if i have user that can access only one type of node and main container that shows all nodes i have a problem and have to make some workarounds. Think this is one of critical things that needs to be solved.

Adriadrop Drupal development