Closed (fixed)
Project:
Menu Per Role
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
19 Jun 2007 at 02:40 UTC
Updated:
20 Sep 2010 at 06:20 UTC
If a menu item points to a node controlled by Taxonomy Access Control, it would make sense for the menu to just reflect that node's permissions as already assigned by TAC. It is unlikely that one would ever need to assign different permissions to the menu item:
Right now I am making double effort by modifying access permissions on the node and on the menu item. Not only does this take more time, it is more error prone because it could allow either of the above problems to occur.
Comments
Comment #1
fagoyeah. that would be nice - but it would better be done as core patch.. (if it is not already in HEAD).
although, if someone would contribute a patch, which detects node paths and adds node access support, I'd be happy to include it.
Comment #2
aren cambre commentedComment #3
AlexisWilke commentedAren,
As far as I know, in 6.x it works like that in the system. Did you have problems with TAC adding menus that should not be there?
Can you give me a complete setup description of what does not work for you?
Thank you.
Alexis
Comment #4
aren cambre commentedThat is satisfactory. I'll mark fixed.
Comment #5
aren cambre commentedOops!
Comment #7
yngvewb commentedHmmm, am I missing something here? taxonomy term pages do no reflect TAC settings in my menus
Comment #8
AlexisWilke commentedThe TAC should reset the nodes permissions, but maybe that could be the problem.
Try resetting your permissions with: Administer » Content management » Post settings
And click on the Build permissions.
Let me know whether that works or not.
Do you have other modules that offer Grants? (i.e. Domain, Organic Groups, To do...) If so, you may have one of those modules giving a positive answer for those nodes.
Thank you.
Alexis
Comment #9
AlexisWilke commentedI'll mark this fixed again. 8-)