We don't want anybody to do it for us - just a ideas on what the best approach would be. The Aros are: Reviewers Approvers Administrators Seniors
The ACO on the other hand is where things get tricky, so we're just trying to get ideas, not code. Because in theory we have 2 separate ones. The normal one would just have the models to control access to the CRUD. The normal ACO would include things like: Projects Proposals BudgetWorksheet Etc. However, we would want to restrict access to Proposals based on the Proposal.status So Full CRUD access on the ACL most of the time, but when the Proposal.status = 'submitted', the CRUD privileges would be gone, and they could only view that. We're just thinking of rolling our own thing on top of the Auth/ACL, but we're even considering dropping the use of the ACL since it doesn't seem to be flexible on that way. We've been rolling our own, but we were going to test out 1.2 Auth/ACL. Since we're also assuming this is a fairly common scenario, we were hoping someone could point us in the right direction. The common scenario being - a web application that changes permissions depending on the status of whatever important item. Like you can only edit certain things before they are finalized. As I said, we are comfortable rolling our own, we're just trying to get ideas for how we would roll this using Cake's things. On Aug 28, 4:45 pm, Rafael Bandeira aka rafaelbandeira3 <[EMAIL PROTECTED]> wrote: > Paste your code and your approach, a test approach at least. I don't > think someone will actually *do* it for you. But many people can point > out what you're missing --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~----------~----~----~----~------~----~------~--~---
