I'm currently developing an application that relies heavily on user privacy.
Firstly, I'm going to set-up an ACL that includes guests being able to view member's profiles and the website's homepage, but nothing else. Registered members would have access to the other areas, along with other ACL groups etc etc. However, my problem occurs when, for example, a SPECIFIC USER (i.e. NOT just an action in a controller) has decided to make their profile private (or even certain parts of their profile). What would be the best way to handle these privacy settings? My initial thought is to place all the access logic inside the beforeFilter() method, after all of the ACL and Auth logic. However, would this significantly affect database performance? In fact, is there a way for custom records to be handled through ACL? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
