Hi John,
I had a look and I could reproduce. I have used this module to hide
existing nodes (denies), that's why I've never run into it.
The root cause is that for the create case, not only [1] but also [2]
gets called (since there is no tree available). ResourceTypePattern [3]
always
Hi,
I'm playing around with the Sling Oak restriction feature and I can't seem to
get it working.
The simple case I'm trying right now is to allow a user 'alice' to have full
access to all nodes at or below nodes with Sling resource type 'foo'. Here's
the test procedure I'm following:
