I'm unable to use this module as it works right now for this reason:
I want an Editor level user to be able to:
* edit and create new nodes for content type Resources
* edit the menu settings for these new Resources pages - only within the Resources menu
* edit existing nodes of the content type Pages
* not edit the menu settings for existing Pages
I have DMA 6.x-1.1 enabled and administer privileges granted to editors for the Resources Menu. Works like a charm for creating new Resources nodes... But now if that editor edits and saves a Page, the existing menu settings (set previously by an admin) are forced into the menu that the Editor level has permission for, thus breaking the main navigation menu.
Adding a content type option so that existing settings stay in place except for content types that the user has permission for would make this module even more useful. It would be fantastic if the Menu Settings didn't even show up except on the content types granted permission.
Thanks for your hard work in creating this module! Let me know what you think...
Is there a different existing module that could be used in combination to create this effect? I didn't find anything.
Comments
Comment #1
squarecandy commentedAfter further digging around, found this module which serves my purposes, though it doesn't technically restrict permissions for user groups as yours does.
http://drupal.org/project/ctm
Sorry to bother...
Comment #2
emdalton commentedI have this problem as well, and the "Menu Settings per Content Type" module won't meet my needs. Is it possible to get a fix? If the menu referenced in the edit page is not one the current user has permission to edit, they should just not see the menu block, rather than forcing the page out of its current menu and into one the user can access. I can't use this module without some kind of logic like that.
Comment #3
dmsmidtI agree, would be a great improvement.