Language Copy vs Live Copy

prohira

15-10-2015

I have a website currently live in bunch of languages like English, Russian, Turkish etc.

Let's say my en_us is my blueprint and I have en_gb, ru_ru as live copies. Now I want to create a "Language Copy" of en_gb website to some other language say "xx_yy".

Why I want for Language Copy is because there is no much language difference in en_gb and xx_yy.

Once I have language copy for xx_yy ready, if I go and make some changes in en_us site and have this rolled out, will those changes be carried over to xx_yy too? or will those last till en_gb only?

View Entire Topic

Paul_McMahon

MVP

15-10-2015

The short answer to you question is that I believe language copy actually kills the live copy relationship so no roll outs will impact the copy. 

In general language copy is intended to be used to create language copies when you want to do something like manual translation and you simply creating the initial copy of the site. Language copy does not create a relationship between source and target the way that Live Copy does. So in the normal scenario where you creating a language copy of your master there is no rollout - you have to maintain any synchronization between the source and target manually. 

In the use case you described where you create a language copy of something that is itself a Live Copy of something else it looks to me as if Language Copy creates the desired copy, but then removes any LiveCopy relationships as the content is copied (both LiveRelationship mixin and the LiveSyncConfig node if present).

What I think you actually want to do is create a live copy not a language copy if you want a rollout impact.