It's a requirement, that xwiki is fully configured after it's bootstrapped.
So our clients get working system right after deploy. That's why why setup
permissions in code.
2016年8月22日(月) 14:51 Vincent Massol :
> > On 19 Aug 2016, at 05:21, Edward Knyshov wrote:
> > Hi. I'm trying to customize permissions in xwiki
> > using ApplicationReadyEventListener.
> > I override some permission in XWikiPreferences XWikiGlobalRights page to
> > get page deletion work by default for all users.
> > https://gist.github.com/edvorg/4e2771ac02c4c64b705127964bc53c64
> > I set up permissions in these functions.
> > https://gist.github.com/edvorg/da7f8e64a46b7bbbf16f953e3fcc0e30
> I’m curious to know why you need to write code to set permissions for all
> users? Why don’t you use the UI?
> > This solutions works fine. But I got a problem with fresh xwiki
> > Sometimes I get fully broken xwiki - all macros shows error. And I have
> > something about admin user not having permission to edit some page:
> > https://gist.github.com/edvorg/1bdec91e5483307696bc68841d2cb1d8
> > I tried to debug all this code but it doesn't make much sense to me. I
> > found that this CacheChecker thing somehow affects the issue. Could
> > point me to possible issues in my solution and maybe describe how this
> > CacheChecker should be used? I would appreciate any help, as we can not
> > rid of xwiki integration bugs for a long time. Thank you!
> users mailing list
users mailing list