I'd invest the time understanding it. It took me nearly a week to figure out in amongst all my other work, but when I did, the light went on. It is pretty clever, it requires little or no logic in your controller methods if done right. And it is hugely scalable beyond that point if required. I found these 2 links useful: http://manual.cakephp.org/chapter/acl http://bakery.cakephp.org/articles/view/user-permissions-and-cakephp-acl#comments Rgds,Howard
On 6/9/07, Ketan Patel <[EMAIL PROTECTED]> wrote: > > I have a site where a user creates certain items. I want that user > himself can CRUD his own profile and other users can only READ this > user profile. Similarly, the user who created the item has CRUD rights > over that item and other users can only READ. Is ACL an overkill for > such simple task or should I simply cook up something on my own which > would do this job. I can do it, its just that I am not sure if I > should use ACL or my own checking to do the above control. > > What do you guys suggest? > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
