Posted by fizk on October 14, 2009 at 4:02pm
Jump to:
| Project: | Content Access |
| Version: | 6.x-1.2 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Issue Summary
I'm using the Private module to allow users to make their own nodes private. For some reason, Content_Access is interfering with Private's ability to make a node private.
I'd like to use these two modules together. Private would allow the user to simply check a box, "Make this private", while Content_Access would allow the user to grant specific users access via ACL. The ACL should only take affect if the node were marked private.
Yonas
Comments
#1
@fizk Did you investigate whether content access module could be improved with a contrib/addon module to implement a private-alike checkbox? This could be done perhaps by implementing a combination of hook_form_alter and hook_form_validate/hook_form_submit.
#2
Download the current Devel module, enable the Devel Node Access (DNA) module, locate the "Devel Node Access debug mode" checkbox at admin/settings/devel#edit-devel-node-access-debug-mode, and turn it on. (You may have to manually put the two DNA blocks into the Footer region if they're not visible.) This will show you how the various node access modules interact with your nodes.
If you need help, pick ONE node that is misbehaving, look at it using an account that can see the node (and that should NOT have access if that's your problem), and attach a screenshot of the DNA information.
#3