I would keep the functionality in separate controllers, not bloat your Users one just because you want to access the User model. To ensure that users cannot view/edit someone elses data you just need to incorporate this into whatever ACL you use. For our application I have a function in app_model called isUserOwned( $user_id, $row_id ), which just does a lookup to see if the requested row is owned by the passed user id. This can easily be included in all my controller actions before allowing the request to proceed.
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
