hi thomas, > something I have in mind, the only restriction for now is how the Admin > class are used by the routing and it is not hard to change. But for now I am > focused on the security layer with ACL.
i played with the adminbundle today (some general follows in a separate thread). i found nothing on permission schemas in your tutorial. does adminbundle allow to control who is allowed to edit / create / delete what? if so, would be awesome if you can explain how to do things like: * restrict admin per entity, based on a user role * fine grained permission control, like user in this role can only edit content that he created, but not content from other people part of this could be handled with acls and the rest in custom controllers for the entities. but would be a lot of typing redundant stuff probably, and the user would see links for things he is not allowed to do - not user friendly... cheers,david -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
