Hi Sean,
what version of Magnolia are we talking about here?
Just a simple test:
- login to demoauthor instance as "eric" (editor)
- activate a page
- once a version is created, try to view it
==> you can see the versions.
If you login as a superuser and check Eric's permissions, you will see that he 
has restricted access to root as well (via role demo-project-editor).

The only permission you need to give is to access the node itself (/$) but not 
anything underneath. 
Cheers,
Jan

On May 21, 2010, at 10:27 PM, McMains, Sean A wrote:

> Ok, rooting through the log files demonstrated that the version information 
> is store in the website repository at /jcr:system/jcr:versionStorage/.
> 
> “No problem!” I thought. “I’ll just add read permissions to that path and its 
> subnodes to our editor role.”
> 
> Unfortunately, when I try to grant read permissions to 
> “/jcr:system/jcr:versionStorage/”, only the bit up to the first colon gets 
> saved. When I reopen the dialog, all it has is “/jcr”, which obviously 
> doesn’t do the trick.
> 
> Is there a workaround for this? Or another approach I should be taking? The 
> only way I can see to provide the necessary access for versioning at this 
> point is to give the editor role access to the whole website repository, 
> which we don’t want, since it will expose all of the other websites in our 
> system to them.
> 
> Thanks for any info,
> Sean
> 
> 
> On 5/21/10 1:33 PM, "Sean McMains" <[email protected]> wrote:
> 
> We’re automatically creating versions of all of our changed content each 
> night. That seems to work just fine for us admins — we can see all the 
> versions and work with them as we’d expect.
> 
> Unfortunately, the site authors, who have more limited access rights, only 
> have the “Date” column populated in the Versions window — they apparently do 
> not have the appropriate rights to be able to retrieve the Name of the 
> version and the User who set it up.
> 
> I’m experimenting a bit with the permissions to see if I can figure out 
> what’s necessary by process of elimination, but if anyone knows offhand what 
> permissions are necessary to have access to the version info, it would be 
> super-helpful.
> 
> Thanks in advance for any help,
> Sean 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
> 
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------

-  
Best regards,

Jan Haderka, PhD.
Magnolia International Ltd.

http://www.magnolia-cms.com
http://twitter.com/magnolia_cms

You should join us on Facebook:
http://facebook.com/Magnolia

--------------------------------------

Magnolia®  - Simple Open-Source Content Management




----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to