[opencms-dev] small guide to siblings

[Volkmar Emberger]

it's not for different languages. it's for different customers-sites. my 
customers will have backend access.
they are able to see global articles but can't edit them. the article 
are placed in a "global" folder and the sysadmin
decides which article will be give to which customer as sibling. so the 
customers have all different articles from the
same article-pool. but they are not allowed to change them.
i think the best method is to restrict the customers access to the 
folder where the siblings of the global article are...

regards

Dusty_it schrieb:

>If you want to make editable a content in different languages to different
>users and don't want that a user can mess up with the content of another
>language, this is not possible, I tried and found that it's not possible to
>protect different blocks. 
>There's a workaround, that is to define the "locale-available" property and
>set it to the locale desired for the sibling . In this way an editor can
>edit only the locale assigned to that sibling.
>
>In this post 
>http://www.pomegranate.de:9000/cms/forum/viewthread?thread=34 
>you should find all the answers.
>
>Regards
>
>
>Volkmar Emberger wrote:
>  
>
>>hi there,
>>
>>does anyone know a good guide to silbings?
>>is a sibling only a link to a resource in the database? so 2 siblings 
>>share the same permissions and data of one source?
>>
>>i am asking wether its possible to create a sibling and give one part 
>>all rights (edit, publish) and the other part (in another folder)
>>no permissions at all. or is it better to change the permissions for 
>>this folder for the user so he can't gain control over the siblings
>>inside?
>>
>>greedings volkmar emberger
>>
>>_______________________________________________
>>This mail is sent to you from the opencms-dev mailing list
>>To change your list options, or to unsubscribe from the list, please visit
>>http://lists.opencms.org/mailman/listinfo/opencms-dev
>>
>>
>>    
>>
>
>  
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20061030/9095be23/attachment.htm>