Using a combination of Node access user reference and Node View Permissions to make a content type visible only to the referenced user, and additionally a specific role (Facilitator) can see all nodes of this content type. So far, so good. It works as intended. Nobody can access the content except for the referenced user or for users that have the "Facilitator" role.
However, I also have a view defined which pulls multiple nodes. The view is blank for a specific user, even though they have referenced nodes that should pull in this view. Additionally, this view is blank for the Facilitator role. The only user able to use the view is the Administrator.
Within the view, I have tried Access->Role->Facilitator and also Permissions->View Published Content.
Should what I'm trying to do work? Or am I trying to use this module in a way that is not intended?
I see on the main page that Devel node access can help in troubleshooting, but I don't know how.
Comments
Comment #2
aajones commentedJust checking in to see if more information is needed. Is there a different/preferred method for seeking support on this module?
Comment #3
aajones commentedI have disabled the node view permissions module, and now I have almost what I need. Any user that is referenced in a node will have permission to view that node, but if they are not referenced, they will not have permissions to view that node. My view now works correctly. It pulls the nodes that the user will have access to view. Nodes that the user cannot view do not appear in the views listing.
The final thing I am missing is the ability to have a different role, Facilitator, that can use the view and see all of the nodes.
At this point I have tried node view permissions, and nodetype_access . As soon as I enable them, the view stops working. It is blank for all but the Administrator role. Any ideas?
Comment #4
nodecode commentedI have the same exact problem with this module and the node_view_permission module. When both are activated, Views does not show any results for anyone but administrators.
The only solution I found was to uninstall Node View Permissions and install Content Access instead which does exactly what you and I want.