Misbehavior when setting priority and per node access permissions and og
| Project: | Content Access |
| Version: | 5.x-1.3 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
There is a problem when setting a priority for the content access module AND giving per node access permissions AND using og. content access module makes use of acl module to set per node access permissions. However, acl is not using the priority value for the grants, so when you set the priority of the content access module because you are using some other node access module, like organic groups, you might end having strange behaviours, like not having the per node access permissions set on a group post even if content access module has a higher priority.
This is a patch, which works along with another patch for acl, which will set the same priority of content access module to the per node access permission set by this module thru the acl module.
| Attachment | Size |
|---|---|
| content_access.patch | 875 bytes |

#1
I've added support for the patch, which has been added to acl. please test.
#2
Automatically closed -- issue fixed for two weeks with no activity.