[Flow] Policies in different Packages
Aske Ertmann
aske at moc.net
Tue Jan 28 20:57:57 CET 2014
Hey Felix
You can extend other roles and you should also be able to set acts for roles from other packages..
roles:
Editor: [ Acme:Package2 ]
acls:
Acme.Package:
methods:
..
As I read it the best solution sounds like just one role defined in the main package/distribution and then acls in the sub packages..
I haven't used it myself yet though.
/Aske
On Jan 28, 2014, at 8:38 PM, Felix Rupp <felix.rupp at gmail.com> wrote:
> Hey guys,
>
> I have different Flow Packages for my application which separate major functions in.
>
> My problem is, that since 2.0 final, all Policies defined in my main package are unique (but can be used in other packages). I would like to realize a policy structure where I have Roles with same names in different packages. These roles shall be identical in my visual representation in the frontend. The administrators must select the roles for each user and only need to see one "GlobalAdmin" and one "Member" role, not each role from each of my packages.
>
> With the current implementation of the roles, I have to assign 4 different "GlobalAdmin" roles to my user, because he needs to be the admin in each package.
>
> I have a snippet of the resulting select-structure in gist: https://gist.github.com/felixrupp/8674298
> This is the list I receive from the policy manager.
>
> I tried to access the roles from the main package in my additional packages, but then I receive the error, that the roles must not be qualified.
>
> Is there any solution or best practice for this problem? I took a look in Neos 1.0 but just found out, that Neos is realized in one main package (with sub-packages) and has no need for this particular option (which I definitively need).
>
>
> I would be happy if anyone has insights or any funky ideas :) !
>
>
> Many greetings
>
> Felix Rupp
>
>
>
> _______________________________________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
More information about the Flow
mailing list