Closed (won't fix)
Project:
Content Access
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Oct 2010 at 12:27 UTC
Updated:
24 May 2020 at 13:23 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
giorgoskthis fixes the problem
I did not seem to find a better way to do it (from the acl api)
Comment #2
salvisThis is very inefficient. Please open an issue in the ACL queue and supply patches (for D7 and D6) with a new function acl_delete_acls_by_name($module, $names), where $names is an array.
Comment #3
good_man commentedThis ACL issue, I'm closing this now, reopen if you have new info.
Comment #4
crea commentedStill relevant
Comment #5
salvisACL is just an API module. It provides services to create records and services to delete records.
Every client module that uses the former should also use the latter. ACL will not try to guess the intentions of the client.
If the ACL API needs to be enhanced, then see #2.
Comment #6
crea commented@good_man, salvis
I hope you guys agree on a solution. It's a shame when issues get silently closed.
Comment #7
crea commentedImplementing module taking care about it's own ACLs makes sense. So I agree with salvis.
Content Access should delete his own per-node ACL in nodeapi delete hook. ACL module can't do that because it can't know if implementing module wants to reuse ACL or not.
Comment #8
gisle