Hi, I found some ACL tutorials on aranworld.com [1] that has been the best lecture so far to clear my doubts and the nice example application is of great help. But I still have a couple of questions that still unanswered to me and I hope someone here can shed a light on them:
1. That tutorial, like the others, just talk about how to handle authorization with CRUD methods, but how do I control other methods that aren't named create, read, update or delete ? I know that view and index actions are considered read actions, so there's no problem with those two, but for example, if I have an action on a controller called register, how can I handle permissions for that one ? or if I have an action called showLastRegisteredUsers which isn't index nor view actions but is also a custom read action, how should it be referenced when creating it's ACO and assigning access permissions to it on the aros_acos table? which type of authorization should I use on the Auth module in this case ? CRUD or actions ? 2. What about access to admin actions when admin routing is enabled ? should they be treated as standard actions but all being referenced on the ACL tables as admin_* ? Any tips that can help me clear my doubts will be greatly appreciated. [1] http://aranworld.com/article/161/cakephp-acl-tutorial-what-is-it Cheers, -- Juan Luis Baptiste --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
