On Nov 9, 12:44 pm, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> sry for the echo. i don't know how i missed your last post. i usually
> just read from my mail client and with so many mails it can be a mess.
>
> anyway. why can't define exceptions? any allow/deny for a user should
> overwrite any group setting. so should look like:
>
> UserGroup (Users) -> allow -> editMyProfile
> User ( X ) that belongs to UserGroup(User) -> deny -> editMyProfile
> (or allow edit all profiles)
> the last one should overwrite the first one
>
> in this case should work, but maybe you're thinking at a different
> situation. what is it?
I'm not talking about what's possible with ACL, but what's possible by
default using cakes own auth component setup with action level checks.
https://trac.cakephp.org/browser/trunk/cake/1.2.x.x/cake/libs/controller/components/auth.php?rev=5874#L660
If you define action level acl checks, that's what you get. There
would be no (pseudo examples) "can User X access Posts/view/1" only
"can User X access Posts/view" This is what I understand to be "per
record" rules and what I understood you meant with your first post,
your above example is of course possible but isn't a "per record"
rule, so perhaps it's just semantics.
hth,
AD
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
