croogo/croogo — comment on commit 5f75bd959ee44ba740304fb58ccc1106e5e62080
File: Plugin/Install/Config/Data/AcoData.php line 1092
By rchavik:

I'm double checking the docs now.

- However, recalling my previous work on 'parental-role' branch, this would not allow us to have one role (that governs plugin ACOS) inheriting permissions from another (because of the plugin path checking). Eg:

Role `ContentManager` has Nodes/* (shortened for clarity)
Role `GalleryManager` has Gallery/*

But we can make `GalleryManager` inherit permissions from `ContentManager` role using `cake acl setparent aro GalleryManager ContentManager`. This allows easier management because we don't have to explicitly give permissions to Nodes/* again.

Having permission inheritance is a great thing when we have many roles (I had a system with 6 roles)

- I think the original value for the 'alias' is already correct. Only the 'action name', or the 'controller name' is needed. ACL will traverse the tree, and construct the path from the alias on runtime. For example, run this on previous database version: `cake acl getpath aco Nodes/admin_index`, and you will get:

```
rachman@fingolfin $ cake acl getpath aco Nodes/admin_index

Welcome to CakePHP v2.1.0-dev
Console
---------------------------------------------------------------
App : croogo
Path: /home/rachman/work/personal/deploy/croogo/
---------------------------------------------------------------
Path:
---------------------------------------------------------------
[1] controllers
[67] Nodes
[68] admin_index
```
Using the new alias scheme, i think it will look like:

```
---------------------------------------------------------------
Path:
---------------------------------------------------------------
[1] controllers
[68] controllers/Nodes/admin_index
```

- I'm pretty sure this will break compatibility with default cake acl (i will test this), and we would lose compatibility with other plugins that uses it, like the great acl_extras by @markstory

- RC