0
votes

I'm building a large Drupal site with deep menus. I'd like to give my client a better interface for finding the menu parent item. With hundreds of items in the parent selector, it soon becomes really hard to find what you need.

I've broken up my menus into "Primary Links" and 6 different product category menus. That helps when you're in admin/build/menu... you can narrow down your choices.

But when creating/editing a page, I'd love to find a way to make the choices simpler. Is there a module available to place the menus into separate parent item selectors?

3
To clarify, I think you are talking only about the dropdown in the node edit form, not about the menu editing itself.donquixote
Yes, the dropdown in the node edit form.Mark

3 Answers

1
votes

Menu Select beta module was just released. It replaces the default menu parent item select on node edit forms with an expandable hierarchy and autoselect field. It also displays a preview breadcrumb above the selection.

1
votes

Take a look at the Menu Per Role module. I hope this helps you

And I just Finished Menu Auto Complete module . which will change your menu interface to auto complete .

Some Instructions :- if you have menu as the following

parent1 
 sub1
    subsub1
    subsub2
    subsub3
 sub2
 sub3
parent2
parent3 
parent4

you should know that the parents or the first elements like (parent1, parent2, parent3..) are always prefixed with "-- ".

so if you are going to search for "parent2" you should search for "-- par" and the menu auto complete will suggest all the parent elements that begin with "par"....if you are searching for "sub1" you should prefix it with "---- " .. if you are searching for "subsub1" you should prefix it with "------ "...and so on

sorry for my bad english && format...hop that will help u

0
votes

Two modules you might find helpful:
Menuless Node Type
Menu settings per content type

I generally prefer the first one, which just removes the menu dropdown. The second one allows to enable only specific menus to choose from per node type.


You might also consider to create separate menus per language, although this does not directly help your cause, unless you want to do some custom module writing.

An interesting future module would be to provide a different form element for this, either an autocomplete textfield, or a popup based on ajax. Anything to reduce the html load on the node edit page.