Hi Tom,
I had this problem too.
I think I solved it
See http://jira.magnolia.info/browse/MAGNOLIA-897
Couldn't do it without you ;)
Thanks
Stojan
TomJensen wrote:
I decided to do some stepping through the code and figured out that the
AccessManager is not allowing permission, but I'm not sure why it would
refuse permission when I'm logged in as superuser. I can see at the
jackrabbit level that there are a bunch of items returned, but they all
get filtered out by the AccessManager. Here's the line in question:
boolean isAllowed =
this.accessManager.isGranted(Path.getAbsolutePath(node.getPath()),
Permission.READ);
That is line 92 in i.m.c.c.search.QueryResultImpl and isAllowed is
always false. I tried walking through the accessManager code but that
started getting really deep for me with Permission objects and Patterns
and the length of the patterns having some sort of bearing on
determining permissions.
I would wonder if I had some odd permission, and I did check and confirm
that the superuser has read/write permission on '/'. I'm assuming
something isn't set right somewhere on my system but I have no clue how
to interpret the Permission and Pattern objects and what's going on in
the AccessManager.isGranted() method to track it down.
Can anyone advise on what I can do to track down why AccessManager is
always refusing permission in this situation?
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
