[opencms-dev] R: ade and multilanguage best practices

[Stephan Schrader]

Hi Lisa,

it depends on your use case or security restrictions. If you're using
siblings and when publishing a resource, all other translations (siblings)
will get also published.

Our best practice is, if you have few editors managing all the content; use
siblings. If you have editors managing only one or more translations use
real copies.

E.g.: Assume you at first level a country and the second level the language:
- ch
- de
- it
- fr
- it
- it
- en
Editor A manages "ch", but must not edit "it" than use siblings under "ch".
So ch-de, ch-it, ch-fr will share the same content. On the other hand, if
you would siblings also for it-it, than Editor A can publish it-it.

Hope that makes it more clear.

Stephan


2014-03-13 9:39 GMT+01:00 <lruggeri at maticad.it>:

> Hi Arash,
>
> I agree with you. But I cannot understand one thing. What is, in your
> opinion, the purpose of having siblings and store xml content of different
> languages in the same file (to clarify they are translations of the same
> content I think) if I cannot use these features?
>
>
>
> What is not clear to me is the workflow Alkakon has in mind when dealing
> with multilanguage sites and ade.
>
> Untill now I used to create one content file in the main language, then
> copy it as a sibling to the other language folders.
>
>
>
> Bye, Lisa
>
>
>
> *Da:* opencms-dev-bounces at opencms.org [mailto:
> opencms-dev-bounces at opencms.org] *Per conto di *Arash Kaffamanesh
> *Inviato:* mercoledì 12 marzo 2014 18.54
> *A:* The OpenCms mailing list
> *Oggetto:* Re: [opencms-dev] ade and multilanguage best practices
>
>
>
> Lisa,
>
>
>
> if you want to restrict write permissions to specific language content
> elements, the only way is most probably to go with Example 2.
>
> But in this scenario you can't use siblings for your container pages or
> use the same content element and use the "copy language" function.
>
>
>
> Kind Regards,
>
> Arash
>
>
> Like <https://www.facebook.com/cloudssky> | Follow<https://twitter.com/CLOUDSSKYONE>
>  | Build your CloudSite with OpenCms OCCX<http://cloudssky.com/en/cloud_services/cloudsites.html>
>
>
>
>
>
> On Wed, Mar 12, 2014 at 5:59 PM, <lruggeri at maticad.it> wrote:
>
> Hello to everyone.
>
> I'm trying to extend an old opencms based website with ade functionality.
>
> Which is the best approach of handling multiple languages with ade, and
> grant translator permissions to edit just their language?
>
>
>
> Example 1:
>
> /.content
>
> /it
>
> /de
>
>
>
> I create  a containerpage for inside /it folder and populate it. This will
> create content items inside .content root folder.
>
> I can then copy the container page to /de folder. The references to
> content items will remain valid.
>
> With this approach I can set language based permission just on the
> container pages, not the content items. Is it right?
>
>
>
> Example 2:
>
> /it
>
>    .content/
>
> /de
>
>    .content/
>
> With this approach the  containerpages cannot be easily copied because
> they reference content inside the language folder.
>
> So each content editor is responsible for maintaining a completely
> independent version of the site. This allows to grant permission on each
> language but can be very hard to maintain.
>
>
>
> I don't need extreme flexibility, but would like to understand how to set
> up a configuration that is easy to maintain.
>
> Do you have any suggestions or previous experience with this topic?
>
>
>
> Thank you,
>
> Lisa
>
>
>
>
> _______________________________________________
> 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/cgi-bin/mailman/listinfo/opencms-dev
>
>
>
>
>
> _______________________________________________
> 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/cgi-bin/mailman/listinfo/opencms-dev
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20140313/f73f1305/attachment.htm>