Question: Does this work with the node edit form?
greg.harvey - November 6, 2009 - 15:20
| Project: | Menu per Role |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | AlexisWilke |
| Status: | closed |
Jump to:
Description
Hi,
I can (and will) download and test this module, but I'm wondering if it works with the node edit form (e.g. hides those menu items from being selectable under the menu settings on a node)? Might be useful to clarify on the project page.
I'm looking at this because it's linked to from the menu_stp module, which seems to be broken for D6 - but it seems to imply this module does *not* cover the node edit form. Similarly, the delegate_menu_admin module seems broken too. Shame really - I'm just looking for a way in D6 to restrict the items available to some users when managing menus, without having to write code myself, but all the modules for this use case seem to fail. I would've thought it would be a common requirement. =(
#1
Greg,
Are you really just trying to hide menu entries? Because this module is really only about that and not to protect the destination nodes.
It seems to me that this is not generally necessary on such a common basis, but maybe your site is.
At this time, it only shows in the menu edit form. But it certainly wouldn't take much to also show the form in the node form as a sub-fieldset of the menu fieldset. Although, by default I'd probably turn that feature off. So you'd have to edit your node type to turn it on.
Thank you.
Alexis Wilke
#2
Hi,
Yes - I only want to hide items. The specific situation is admin_menu adds an *enormous* menu to the Drupal menus section, which shows on the node edit pull down too when selecting parents. I still want my users to have *access* to admin_menu's menu (they need it to use it) but I don't want it to appear and confuse them when editing nodes. The same is true of the default Navigation menu in many scenarios.
Hope that makes sense. Maybe this could be switched to a feature request instead, if you think it makes sense and wouldn't be difficult to achieve? =)
#3
Greg,
Here you go. The -dev should have the change within 12h.
Thank you.
Alexis Wilke
#4
Wow, thank you! That was incredibly quick! =)
#5
This now causes all submission of nodes to have the ugly error message about needing to apply a patch, even if a new menu item is not being created.
#6
Well... then install the patch! 8-)
Okay... j/k
Could you post the exact message?
There is something about a patch in this module but it should not wake up.
Thank you.
Alexis
#7
Okay, I uploaded a patch for that problem. It should be available within the next 12h.
Thank you.
Alexis Wilke
#8
Automatically closed -- issue fixed for 2 weeks with no activity.