Miraculously, I now understand ACL. I have hierachies of ACOs and AROs and such like with groups of users and essentially lists of controllers. I've demonstrated various deny/allow situations. Lucky me!
The 2 or 3 instances of documentation on said topic describe having a central "checkAccess()" method in AppController. eg see http://manual.cakephp.org/chapter/acl http://bakery.cakephp.org/articles/view/user-permissions-and-cakephp-acl#comments My ACO's that are the same name as the controllers as per the second url, making it easy to establish this from the object params. What I'm asking is, should I expect to have to put a checkAccess() call in almost every single controller method? It would call the method with the appropriate C/R/U/D label required to run the Acl->check() method. It just doesn't seem very elegant having a call in every single method compared to other cake concepts. Am I missing something? I thought about beforeFilter() but then the problem becomes, how do you know that method "xyz()" should be checked against (say) "update"??? Hope that all makes sense; thanks, Howard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
