Hi.
On Thu, Aug 19, 2010 at 6:15 AM, David Glick davidgl...@groundwire.org wrote:
As an alternative to requiring calling setDefaultRoles/addPermission at
import time, I suggest that we add an optional roles attribute to the
permission directive. This would then be used when the directive is
Hi,
On 19 August 2010 16:46, Hanno Schlichting ha...@hannosch.eu wrote:
Hi.
On Thu, Aug 19, 2010 at 6:15 AM, David Glick davidgl...@groundwire.org
wrote:
As an alternative to requiring calling setDefaultRoles/addPermission at
import time, I suggest that we add an optional roles attribute
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/19/10 09:46 , Hanno Schlichting wrote:
Can roles currently contain whitespace? Like Awesome People?
If so, we should go for nested nodes:
permission id=my.NewPermission title=My new permission
roleManager/role
roleSiteAdmin/role
On 8/19/10 12:46 AM, Hanno Schlichting wrote:
Hi.
On Thu, Aug 19, 2010 at 6:15 AM, David Glick davidgl...@groundwire.org
wrote:
As an alternative to requiring calling setDefaultRoles/addPermission at
import time, I suggest that we add an optional roles attribute to the
permission
Proposal:
As an alternative to requiring calling setDefaultRoles/addPermission at
import time, I suggest that we add an optional roles attribute to the
permission directive. This would then be used when the directive is
executed, instead of the current hard-coded Manager setting.
