Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retrieving available fields from (Mutable)AclInterface #3136

havvg opened this issue Jan 17, 2012 · 2 comments


None yet
2 participants
Copy link

commented Jan 17, 2012

I'm implementing the MutableAclInterface and MutableAclProviderInterface separated from there immutable counterparts. Right now I'm stuck with the question on how to retrieve the available fields an ACL provides (both class and object based)?


The question rises when implementing the MutableAclProviderInterface::updateAcl(), since there may be new FieldEntry given on that MutableAcl to be persisted, but the MutableAclInterface (extending the AclInterface) does not provide a method to retrieve the list of fields available.
The only methods available are getClassFieldAces($field) and getObjectFieldAces($field) where the provider already needs to know the existing fields or the other way around it would be required to know the domain object - both shouldn't be the case.


Adding AclInterface::getFields() returning an array of string, the currently associated fields. The returned list does not represent the complete list of fields available on the domain object/class, but only those used/known by the acl.


This comment has been minimized.

Copy link

commented Apr 10, 2014

@havvg have you eventually found a different solution for your use case? This issue has been open for two years now. Considering no feedback nor related PRs maybe it's time to close?


This comment has been minimized.

Copy link
Contributor Author

commented Apr 13, 2014

Well, I coupled the implementation of MutableAclProviderInterface with that of the AclInterface. This implementation provides the required method, so it's kinda solved.

I'm closing this, as there has been no feedback for two years :)

@havvg havvg closed this Apr 13, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.