Well for your situation, it seems adapted indeed. You will create an aro per group, some of aro will have another aro for parent to inherit parent rights. On the lowest group will not have parent. The you create an Aro per User that has a group aro as parent.
You aco will be the controller/actions. With the ACL behavior you can automate this, when creating a group that will create automatically an Aro. You can also do this when creating a User, and affect the parent aro. The only tricky bit (but easy to make), is when a User changes group. After you will have to set permission on aro - aco (ie: group - controller/action). And yes, if you authorize an action for Guest, Contributor will inherit the Guest authorization. On Jun 28, 7:06 am, José Pablo Orozco Marín <[EMAIL PROTECTED]> wrote: > First, i want to know if the concept (my situation and concept) is > good or not? > > Second, i want to know if: when I use $aro->setParent... this means > that the Aro inherits all the permission of his-her child group? > > Thanks in advance. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
