sonata-project/SonataAdminBundle — pull request #461 by rmsint (2011-12-19 21:28:37+00:00)
Title: Acl

Changes:

- added RoleSecurity handler to be backwards compatible with previous Acl implementation + provide quick security possibility for admins
- changed object ACLs: due to a mistake of me they had the Admin ACL as parent, now a custom parent can be choosen. Fe. inheriting permission from a logical parent object:
- Post Object 1 ACL
- Comment Object 1 ACL
- implemented object isGranted check in the controllers and templates
- updated docs
- DoctrineOrmAdminBundle:
- sonate:admin:generate-object-acl command
- UserBundle:
- split user form in editable roles and readonly roles
- implement custom voter to deny access for __normal users__ to __super-admin__ users

Question:
- check permissions for batch delete action: where do you think this should be done? In the modelmanager or before, in the CRUDController? I think the check should filter the objects with no DELETE access granted. And if objects are filtered, add the amount of filtered messages in a flash message warning or notice.