09-02-2009, 07:55 PM
|
#8 (permalink)
|
|
The Prestige
Join Date: Sep 2007
Location: Sweden, Stockholm
Posts: 1,080
Thanks: 115
|
Quote:
Originally Posted by ioan1k
Why separate the resources into three types and have three separate methods for each one as they are doing the same thing?
|
Because I think that will be the best solution for what I want to accomplish.
What if I have a feature called "blog", that would go into the resource "blog". Then also, I have a page called "blog", that would also be a resource "blog" - but wait, that won't work.. It already exists!
And lastly, how do I store the permissions set by the owner of the blog into the "blog"(as used in $perm->canSee() function which checks if the viewing user can see the "blog" in this case, based on the permission set by the owner)? I can't store it as a resource.. because there are already 2 other "blog" resources..
That is, in my opinion, a flawed system. But maybe I've misunderstood how to use this..
Quote:
Originally Posted by ioan1k
Here are the files to a more advanced ACL System
It has the ability to do the following - Assign resources on a level (1-4) 1 being Guest, 4 being Admin
- Create a parent child relationship for roles and resources
- Resource access is based on the following criteria.
- Role Group Level
- Specific roles granted access or denied access
- Specific users granted access or denied access
- Inherited Permissions for any parent roles
- Inherited permission for any parent resources
You should be able to go through and see how everything works as it is commented very well ... if you have any questions let me know |
Thanks! I'll check it out!
__________________
|
|
|
|