Closed (works as designed)
Project:
Content Access
Version:
7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
16 Mar 2011 at 11:58 UTC
Updated:
6 Nov 2011 at 18:33 UTC
I use D7 and I need to block the access to a node.
If I use "Content Access" on a page, I have to disable "Administer content" for the role of the user.
But if I do so, the user can't change the "Publishing option" of the other nodes.
And "Content Access", if the user has the "Administer content" checkbox flagged, don't let me de-select the check in the node content access page.
Could it be possible that the check would be on "Bypass content access control" checkbox instead the "Administer content" checkbox of the node permission?
Thanks.
Comments
Comment #1
Firewolf commentedWhen "Adminster content" is activated for a role, these users have access to publishing options. Only for the nodes for which they have access via "Content Access". I can still edit the access settings.
When "Bypass content access control" is activated for a role, these user have access to all nodes; the content access module is ignored.
On my test site everything seems to work properly.
Comment #2
salvisThat implementation is correct. It's how Drupal is designed.
You may be able to find an alternative to the Published flag, see #1069928: Revision permissions? for example.
Comment #3
David4514 commentedI'm still having trouble understanding how to combine Content Access (the module) and Administer Content (core permissions)
Let's say
I cannot make this work. Once a member has any role which gives them Administer Content rights, they have permission to Administer Content on ALL content they have access to.
What I would like is the ability to control through Content Access which user,s by role, can also Administer Content (publish, promote, sticky, ...)
Comment #4
salvis@David4514:
This is unlikely to get you any response. This thread is closed (no one sees it) and it's not about what you want to talk about.
Here's my recommendation: Start a new thread, with a good title, and present a concrete use case rather than an abstract jumble of letters.