Jump to:
| Project: | NodeSymlinks |
| Version: | 6.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed |
Issue Summary
First I want to thank you for developing this module. It opens up many possibilities when using the menu to structure content. I am very excited to see it. It is a great tool for smaller sites that want to post a page in a few locations, but don't want a full-blown taxonomy structure. Potentially addresses a variety of issues: #321453: when multiple menu items point to the same node..., #317786: multiparent capability?
I want to suggest combining the User Interface with the Menu Settings Fieldset. You're essentially creating the ability to make "multiple menu items" (at least from the point of view of a non-drupaller), with the first menu item being the "real" menu item. If you could combine the menu settings with node symlinks, and put the menu item as the first symlink, that might be very helpful. (though I'm sure there are other better ways to handle this)
Second, I recommend checking to see if menu by content type has restricted the the content type to a particular menu, like primary links. The module shows all menus, regardless of whether their access has been restricted for the user.
Thanks!
Comments
#1
#236053: Ability to add multiple menu parents per node in node edit Menu Settings
#2
Thanks for suggestions. I plan some integration with Node Menu Settings, because first I need one "original" content with no "NOINDEX" before I allow user to make "duplicates".
#3
Great module man. We are going to make heavy use of this.
I am currently adding in some of my own code that we need to autoassign taxonomy based on menu/NAT stuff... but in the meantime, can we possibly have this added in an update?
1. hook_perm() - Not every role should be privy to using nodesymlink. Has access, load code - show form, no access, hide additional links form.
2. node types - Some may want to exclude this module entirely from certain node types.
3. Default menu parent - Options to say where additional menu links should be stored, presenting only that option. Primary Links, Secondary, custom menus. Some sites menu tree may be excessively large to show everything in a drop down.
#4
Hi gh0st25,
1. I'm not sure if the hook_perm is really necessary, Nodesymlinks is "addition" to Menu Settings menu, so it displays only for users which has Administer menu permissions. I think that when you give some user "administer menu" rights, he can possibly add unlimited number menu items. I don't see really need of finer grained access control. Do you?
2. Yes, but again I design Nodesymlinks as addtion to Menu Settings, you can hide whole menu settings fieldset using this modules:
Menu Settings per Content Type
Menuless Node Type
3. There is couple of module which is near what do you need this. They are reducing menu by limitting access by role. I'm not sure if some integration with nodesymlinks is needed:
Menu Subtree Permissions
Delegate Menu Administration
I agree that some control which part of menu can be displayed and default parent can be useful.
#5