I really would not want to allow client to edit menus manually, mostly because I dont want to teach them how to. An awesome feature would be content type "Firstchild". It would have Title and parent item. Thats it. Create it, menu item is created, you can stack other content types on it. Delete it and menu item is gone, children floats in limbo (same as if 'page' node with menu item would be deleted).

CommentFileSizeAuthor
#3 Create_Page_1291443704450.png27.02 KBmansspams
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mansspams’s picture

Title: UX improvement - create menu item from node » UX improvement - create menu item from node form

Better yet, special content type is not needed. Just option to make node a Firstchild and possibility to add link title, right within menu settings fieldgroup. Checking this box on new node would insert two menu items (firstchild pointing to default node menu item if set and default node item under firstchild) and setting this box on existing node would check if some other node was firstchild before and change records accordingly.

mansspams’s picture

Assigned: Unassigned » mansspams

I will try to come up with some code.

mansspams’s picture

Something along these lines. anrikun? Users? Anyone else finds this useful?

anrikun’s picture

Isn't this about Drupal 7 version?

mansspams’s picture

no, why? Its D6.

anrikun’s picture

Your screenshot looks like Drupal 7, doesn't it?

mansspams’s picture

no, its D6 with Vertical Tabs module.

anrikun’s picture

Then could you please post a screenshot using a default configuration (Garland + no Vertical Tabs)?
Thank you.

dgastudio’s picture

i think that is better to add a checkbox for each menu item on the page admin/structure/menu/manage/name_of_your_menu.

it will be much more faster and visually better to use.