Active
Project:
Menu Firstchild
Version:
6.x-1.6
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
4 Dec 2010 at 05:40 UTC
Updated:
28 Jul 2011 at 06:03 UTC
Jump to comment: Most recent file
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).
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | Create_Page_1291443704450.png | 27.02 KB | henrijs.seso |
Comments
Comment #1
henrijs.seso commentedBetter 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.
Comment #2
henrijs.seso commentedI will try to come up with some code.
Comment #3
henrijs.seso commentedSomething along these lines. anrikun? Users? Anyone else finds this useful?
Comment #4
anrikun commentedIsn't this about Drupal 7 version?
Comment #5
henrijs.seso commentedno, why? Its D6.
Comment #6
anrikun commentedYour screenshot looks like Drupal 7, doesn't it?
Comment #7
henrijs.seso commentedno, its D6 with Vertical Tabs module.
Comment #8
anrikun commentedThen could you please post a screenshot using a default configuration (Garland + no Vertical Tabs)?
Thank you.
Comment #9
dgastudio commentedi 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.