You do not have permission to create a Resource in this location - aaarrrggg!!

Are you sure you were logged in as the admin Super User? If so, it sounds like that would be a bug.

Yes, absolutely certain. I will report it as a bug. Maybe it’s as simple as ">" rather than ">="

I cannot reproduce this problem at all. I tested with a GroupAdmin Role with authority of 1 and all the ACLs seemed to be working as expected. Did you make sure and clear the cache and flush sessions before testing this?

Quote from: OpenGeek at Oct 05, 2010, 09:38 AM

I cannot reproduce this problem at all. I tested with a GroupAdmin Role with authority of 1 and all the ACLs seemed to be working as expected. Did you make sure and clear the cache and flush sessions before testing this?

I had the same problem, with 2.0.2-pl on XAMPP and Windows 7. Flushed permissions and cleared cache, no success. Even if I created the document somewhere else and then try to move it, i would get the same error message.

Though it works with the "ressource" policy, so it’s not really a problem anymore. But one would think it should work with the admin policy as well.

Quote from: rabimoe at Oct 06, 2010, 09:02 AM

Though it works with the "ressource" policy, so it’s not really a problem anymore. But one would think it should work with the admin policy as well.

Nope. The Admin policy is for Context ACLs ONLY. The Resource policy has important permissions that do not apply to Context ACLs, only to Resource Group ACLs.

I can’t reproduce the problem anymore. I changed the minimum role which corrected it. I reported it as a bug. They couldn’t reproduce it. I changed minimum role back to 0 and it still was OK. But I had also cleared permissions, which I thought I had tried before. So my "scientific" method was flawed.

Sometimes you also have to flush all sessions (or log out and back in).

Its a bug!

Do you have the bug #?
I realised that ive stumble upon same issue, but in a resource.

When one create a resource, and attached a resourcegroup to it.
Then you will realise you can never create a child resource below it.

----------------------------
Then i found the problem.
The solution is to add this to the user group (administrator in your case):
+ resource group: [your resource group]
+ min role: [administrator]
+ access policy: [Resource]
+ context: mgr


But then again, why would this be working, but access policy of :[Administrator] not working?
Its weird, only effect create new document.

Hope it helps, cheers