DCR localization

for the content localization, I used the ootb feature and added few xmls. for e.g.

Base xml:- abc.xml
localized xmls:- abc_en_US.xml and abc_en_GB.xml

Functionality works wonderful on the site publisher level. I can see my localized content on .page and on preview server. But then I publish my content to the runtime environment and now I am always seeing the content of my base xml i.e. abc.xml

My question is what configuration is needed on the runtime environment in order to fetch the DCR dynamically exactly like it works in site publisher environment. Am i missing some step. please guide.

Also PLC doesnt attach localized xmls when you publish the page. so it is always abc.xml

Find more posts tagged with

Comments

Rick Poulin

My question is what configuration is needed on the runtime environment in order to fetch the DCR dynamically exactly like it works in site publisher environment. Am i missing some step. please guide.

Is your .page also localized or are you using an external to dynamically fetch a different flavour of the selected DCR based on context?

Also PLC doesnt attach localized xmls when you publish the page. so it is always abc.xml

The answer sorta depends on the question above, but the page you're publishing only has the master DCR as its dependency. If you were publishing the master DCR, I'll bet the localizations would come along for the ride. You might just have to create a custom task to pull second-order dependencies like that.

kdr

My .page is localized.

One thing I could see is when we localize the assets (DCR's in this case), it gets copied to branch_locale folder. ootb feature suggests that you rename the content dcr as per the locale. so, In my parent folder or the data folder i renamed the dcrs as per locale and now my child folder which has localized DCR's are untouched. So, I am confused here.

kdr

More clarity on DCR structure:-

so the data folder has:-

abc.xml

after creating a child site , now the DCR's are copied to

data/branch_en_GB folder

file name is the same:- abc.xml

In order to localize the DCR's , the data folder now has three files

abc.xml
abc_en_US.xml
abc_en_GB.xml

where as the DCR's in data/branch_en_GB is as is.

Rick Poulin

My .page is localized.

K, so this means that when you publish master abc.page, DCR abc.xml should come with. When you publish GB abc.page, then DCR GB/abc.xml should come with.

This also means that on the runtime, you'll only see the GB content if you get to the UK page. It sounds like you're always hitting the master locale because you don't have anything in place to send you to the GB locale. That's not OOTB unless you've mapped the different locales to different (sub)domains.

One thing I could see is when we localize the assets (DCR's in this case), it gets copied to branch_locale folder. ootb feature suggests that you rename the content dcr as per the locale. so, In my parent folder or the data folder i renamed the dcrs as per locale and now my child folder which has localized DCR's are untouched. So, I am confused here.

Renaming the master locale file will break the relationships with its children. You're only allowed to rename the child files. If you've renamed the parent, then publishing it won't bring the children along because those relationships were lost.

As for your latest post, I don't know if copying the DCRs like you have will preserve the dependencies or the sitepub auto-figureoutiness. A 'move' would at least preserve the deps, but you should evaluate whether your use case / requirements actually require you to organize the files in this non-default way because it may cause you some pain (or additional development) now or in the future.

kdr

Okay. Yes its correct that when I have abc.page, I get the abc.xml and GB abc.page I get the GB dcr content. The only question is when I dont have the GB content dcr, component should pull the parent DCR or the default DCR. Fallback sort of rule which fetches the default content if localized content is not present. So what could be the best way to implement this sort of behavior.

Rick Poulin

Okay. Yes its correct that when I have abc.page, I get the abc.xml and GB abc.page I get the GB dcr content. The only question is when I dont have the GB content dcr, component should pull the parent DCR or the default DCR. Fallback sort of rule which fetches the default content if localized content is not present. So what could be the best way to implement this sort of behavior.

If abc.page and abc.xml already exist, then when you localize abc.page it should automatically create a localized abc.xml with a copy of the master locale content. At that point, if you never need to change the localized copy, your author can delete the GB version of abc.xml and change the datum in GB/abc.page to point at master/abc.xml.

If you want anything smarter or more automated, then you'll have to build it custom.

kdr

Ok yes thats the good point. now here instead of Author changing the datum to point to the master xml, I would like to propagate the changes of master to the localized rendering everytime when I do the changes to Master. I can do that probably with the publishing workflow but I am thinking of whether thats the only feasible option.

Rick Poulin

Ok yes thats the good point. now here instead of Author changing the datum to point to the master xml, I would like to propagate the changes of master to the localized rendering everytime when I do the changes to Master. I can do that probably with the publishing workflow but I am thinking of whether thats the only feasible option.

It's not the only option, but it's a pretty good one. You probably don't want to push down changes every time someone hits save, because then the 'undo' gets very complicated. In workflow, you can better control when this happens, e.g. only after the master has been reviewed and approved.

gauravTsDev

Hi kdr,

I have gone through your thread post.I have similar type of required where I trying to figure out how we can OOTB localization for content .Please explain how it can be achived .

Thanks

Gaurav