Hi;
I am trying to set up a manager user role for a blog editor, basically a manager user that can only log in and add/edit/delete blog postings. So far I think I have most things setup correctly but when the blogeditor user logs in they cannot see the document tree.
- To begin with I followed this guide here:
http://bobsguides.com/revolution-permissions.html went through the process about 3 times.
- I did create resource groups & associate them to the editor role for the blog articles, with or without groups, the blogeditor cannot see anything
- I’ve tried flushing caches, sessions, etc...
- I even looked for that udperms_allow root variable and set it to yes.
So everything appears to be working correctly up to a point, the editor can log in and all the ACL permissions I assigned [or revoked] are correct - the resource tree is just completely blank [no resources, elements or files]
I’m thinking it must have something to do with the resource group assignment? [yes - I did move all the associated documents into the appropriate resource group]
The only clues are 2 odd errors:
- when trying to clear the cache as an editor:
Principal 4 does not have permission to load object of class modContext with primary key: web
- if I try to create a new document as an editor:
Also, when I create the blog post resource group and assign it to the editor role, all the blog entries ALSO disappear from the administrator resource tree/browser.
- any thoughts??
- thanks
- sean
PS> While I am on the subject - is there a way to automatically assign new documents from a given template to a specific resource group? i.e. when the editor user logs in and creates a new blog posting, I want that document to be automatically in the blog resource group [or will it inherit that from the user who created it?]
