Unfortunately it's a known bug that turning the cache off will make
ACLs sometimes break :-(. We have no idea what the reason is, but it
is not common that someone would use JSPWiki as a rendering engine but
still wants to use it's own ACL mechanism. Usually the access control
is also replaced.
JSPWiki is not designed to run with the cache off (and the fact that
it's in the jspwiki.properties even as an option is an unfortunate
mistake from us :-(.) I know some people on this list have experience
with these situations, so maybe they could help you?
JSPWiki 3 will have a completely different backend and should not have
these problems at all.
/Janne
On Apr 14, 2009, at 05:10 , guo weizhan wrote:
Thank you for you reply, Here is my situation, I'm using jspwiki as
our
subproject and the parent project also have data cache mechanism, the
jspwiki page will get the data from the parent project, so we want to
disable the jspwiki cache and using the data cache from parent
project.
2009/4/14 Janne Jalkanen <[email protected]>
It's not recommended to turn off the page cache, unless you really
know
what you're doing. If you don't need the cache, turn the cache on,
and set
it to a very small size.
/Janne
On Apr 13, 2009, at 12:58 , guo weizhan wrote:
Hi All,
When I set the usePageCache to false in the jspwiki.properties, the
permission([{ALLOW view wkg}]
) didn't work, have you meet this problem? I'm using version2.8.
Thank you!
