Closed (fixed)
Project:
Hierarchical Select
Version:
5.x-3.0-rc3
Component:
Code - Menu
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
3 Oct 2008 at 14:48 UTC
Updated:
4 Dec 2008 at 00:01 UTC
At www.example.com/admin/build/menu/settings, one can choose to restrict the parent item for new menu entries to "Primary Links". That restriction is picked up by Drupal's own menu parent item selection widget. But it is NOT picked up by the replacement Hierarchical Select Menu widget. Not a big issue for administrators. But ordinary users won't typically understand the effect of selecting "Navigation Links" as the parent for a menu item and it would be nice to prohibit them from even making that choice.
Comments
Comment #1
wim leersI didn't even know that setting existed! It'll require me to reorganize the HS Menu implementation, but I'll implement it.
Comment #2
wim leersDone!
Comment #3
ricardo37 commentedYou are a prince among men for implementing this new feature.
Having tried the new version out, I must report that it is very close, but not quite right. When the parent menu item has been restricted, at admin/build/menu/settings, to "Primary Links", on new nodes the menu-parent hierarchical-selection widget has for options only "None" and whatever other items are currently among the primary links. The widget needs to supply one more option: "Primary Links". Otherwise anyone creating new content cannot use the widget to place the corresponding menu item among the primary links; it can only be located beneath an existing primary link or not at all.
Comment #4
wim leersGood point. I'll provide a
<root>item instead, because otherwise you'd *always* have a first level that consists of a single item, which would be silly.Comment #5
wim leersI opted to not use a
<root>item because then the hierarchy is altered, which might cause confusion.