I have 2 content types A and B, I'm using tac_lite and content access for fine grained access control across my site.
What's happening is, anonymous + authenticated users are ticked to view all/own content of type A, but not of type B.
I have a vocabulary "Access control" from which I have tagged a piece of content from A (nid 1311) and B (nid 1310) with a term "Customer" (tid 138).
I have a role "Content creator" which is ticked to view all/own content for both A and B, and also has the administer nodes permission (or "Administer content"
When content type A has anonymous and authenticated users ticked in the content access screen, the node_access table looks like so:
nid | gid | realm | grant_view | grant_update | grant_delete
------+-----+--------------------+------------+--------------+--------------
1310 | 4 | content_access_rid | 1 | 0 | 0
1310 | 7 | content_access_rid | 1 | 0 | 0
1310 | 138 | tac_lite | 1 | 0 | 0
1311 | 138 | tac_lite | 1 | 0 | 0
When I untick the content access for anon + authenticated and rebuild permissions I get this:
nid | gid | realm | grant_view | grant_update | grant_delete
------+-----+--------------------+------------+--------------+--------------
1310 | 4 | content_access_rid | 1 | 0 | 0
1310 | 7 | content_access_rid | 1 | 0 | 0
1310 | 138 | tac_lite | 1 | 0 | 0
1311 | 4 | content_access_rid | 1 | 0 | 0
1311 | 7 | content_access_rid | 1 | 0 | 0
1311 | 138 | tac_lite | 1 | 0 | 0
In the first instance, my user with the role Content creator, and no access control terms is DENIED access to node 1311, but granted access to 1310. After unticking the anon + authenticated users for type A and rebuilding permissions I am successfully granted access to node 1311.
This definitely seems like a bug to me, I'm running Content Access 7.x-1.2-beta1. To get content access and tac lite working together I'm using hook_node_access_records_alter to drop the priority of normal node grants.
Comments
Comment #1
acbramley commentedBumping priority
Comment #2
gisleThis issue has not received any updates in the previous 7 years. If you believe it to still be relevant, you are encouraged to reopen the issue and update it.
If you got an email about this Issue status update, it is because you at one time (possibly a very long time ago), subscribed to it. To learn how to unsubscribe yourself, please visit: https://www.drupal.org/project/webmasters/issues/3142987