Hi Matteo,

you are really quick and great user/supporter ;-)
Thanks a lot for your contribution. Maybe we
should establish some "Best contributor cup"
and pronounce the winner at Magnolia conference
on September:-) Will you join us?



-  
Best regards,

Zdenek Skodik
Magnolia International Ltd.

  Meet us at the Magnolia Conference
  http://www.magnolia-cms.com/conference

Magnolia®  - Simple Open-Source Content Management


On Čt, 2009-06-18 at 09:46 +0200, Matteo Pelucco wrote:
> Olaf iLink ha scritto:
> > Hello,
> 
> Hi Olaf,
> 
> > ...why can't my editor role log in into the authoring 
> > environment? It doesn't give any error message.
> > What ACL settings do i have to set for an editor that can log in and 
> > edit pages? Setting read/write to the website repository doesn't seem to 
> > be enough?
> 
> it is not enough: you must assign to the role /* on URLs (Get&Post).
> 
> > Another question: do i always have to assign a user to a group, or can i 
> > also leave this empty?
> 
> You are free to decide. It is a best practise to have grouped users, 
> expecially for large companies / large content manager team.
> But it is not mandatory, you can avoid it and assign a role directly.
> 
> > What ACL settings do i have to set to create a publisher, someone that 
> > can access the workflow and activate pages from the website repository? 
> > etc.etc.
> 
> Look at a standard (CE) Magnolia 4.1, you have a good starting point 
> (group "publisher" linked to role "workflow-base").
> 
> HTH,
> Matteo
> 
> 
> ----------------------------------------------------------------
> 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]>
----------------------------------------------------------------

Reply via email to