I have the need for a site where I can define access to individual nodes by user. In this scenario, access by permission or roles is not finite enough. Node_Access has this ability. But when I want to create a view to display the node available to a given user, View's Access setting overrides the permission and roles settings in Node_Access. There is a similar module, Content Access that tries to solve a similar problem. But there are not controls to prioritize or hierarchize how these module's permission settings should subservient to the other modules that deal with permission. If Views would work with these modules, maybe via a Better Access for Views module, that could be one solution. In this situation I could give View's Access setting least priority, thereby saying that having role X is the lowest requirement to get permission to view this node, or in the case of defining by permission, to say "be subservient to the permission settings in Node_Access" or "be to subservient the permission settings in Content Access." The Another solution might be to have a Permission Hierarchy module where you could tell Drupal how to layer permissions. I am willing to sponsor the creation of a solution to this. How can we get this rolling?
↧