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

[lruggeri at maticad.it]

Hi Kai,

yes I tried but it does not work. The locale-available property which is
read when editing a content item is the one of the folder where the content
item is in the vfs, not the one inherited by the containerpage.

 

Bye, Lisa

 

Da: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org]
Per conto di Schliemann, Kai
Inviato: giovedì 13 marzo 2014 15.12
A: The OpenCms mailing list
Oggetto: Re: [opencms-dev] R: ade and multilanguage best practices

 

Hi Lisa,

I know that.

I just thought, that if you drag and drop a content item on a container page
(where on a parent folder the locales-available property is set to “it” or
“de”) and then edit that content item, that in the editor you can only
select the language which is set in locales-available property. If that is
not the case, it won’t help you.

Did you try that?

 

Best regards

Kai

 

Von: opencms-dev-bounces at opencms.org
<mailto:opencms-dev-bounces at opencms.org>
[mailto:opencms-dev-bounces at opencms.org] Im Auftrag von lruggeri at maticad.it
<mailto:lruggeri at maticad.it> 
Gesendet: Donnerstag, 13. März 2014 11:56
An: 'The OpenCms mailing list'
Betreff: [opencms-dev] R: ade and multilanguage best practices

 

Hi Kai,

unfortunately this seems not possible in example 1. Since the content items
are in the root .content folder, only the container pages which resides in
/it and /de folder are affected by locales-available property. The content
items still show all the locales.

 

If this would be possible, could be a reasonable solution in fact.

Bye, Lisa

 

Da: opencms-dev-bounces at opencms.org <mailto:opencms-dev-bounces at opencms.org>
[mailto:opencms-dev-bounces at opencms.org] Per conto di Schliemann, Kai
Inviato: giovedì 13 marzo 2014 11.34
A: The OpenCms mailing list
Oggetto: Re: [opencms-dev] ade and multilanguage best practices

 

Hi Lisa,

you can set the property „locales-available“ on the language folder as a
comma separated list. In the editor only the in this way configured locales
are shown.

 

So considering your example 1 you could set “locales-available” on the “it”
folder to “it” and on the “de” folder to “de”.

 

There is no permission check, doing it that way. But the editor cannot
choose another language in the editor.

 

HTH

Regards

Kai

 

 

 

Von: opencms-dev-bounces at opencms.org
<mailto:opencms-dev-bounces at opencms.org>
[mailto:opencms-dev-bounces at opencms.org] Im Auftrag von lruggeri at maticad.it
<mailto:lruggeri at maticad.it> 
Gesendet: Mittwoch, 12. März 2014 17:59
An: 'The OpenCms mailing list'
Betreff: [opencms-dev] ade and multilanguage best practices

 

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

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20140313/88c64064/attachment.htm>