How to rollout content fragments

ashishkhadpe

22-08-2019

Hi All,

I am creating content fragments in en language and would like to rollout the fragments to other locals. But content fragments are not pages, not sure how this can be achieved.

Please let me know if anyone has any solution on this.

Accepted Solutions (1)

Accepted Solutions (1)

nikunjj81682294

19-12-2019

AEM 6.5.2 has the support for creating MSM live copies for Assets. Here is the documentation around it:

https://docs.adobe.com/content/help/en/experience-manager-64/assets/using/reuse-assets-using-msm.htm...

 

Unfortunately, it doesn't support content fragments yet. Hopefully, Adobe will add this feature in the next releases. 

 

Here is a video of how MSM for assets works with AEM 6.5.2.

https://www.youtube.com/watch?v=GuMopMjpmQk

 

Thanks,

Nikunj Jariwala

 

Answers (10)

Answers (10)

ashishkhadpe

25-08-2019

Yes correct.

Let me explain how we are doing it for normal AEM pages.

We have base site under en local. We then use MSM to rollout the site to other locals. We then provide the rolled out local pages to clay-tablet for translation. We would like to achieve the same for content fragments if it is possible. But as you said content fragments are assets in nature they can not be rolled out.

So generally do we roll out the content service pages?

hamidk92094312

Employee

23-08-2019

In your initial question you mentioned "would like to rollout the fragments to other locals" that means translation. So content fragments are assets in nature so they can not be rolled out individually if that's what you mean.

ashishkhadpe

22-08-2019

Hi Hamid,

My issue is not with getting content fragment translated. It is working fine with me.

My concern is how to rollout the content fragments like we rollout the content pages.

hamidk92094312

Employee

22-08-2019

1. Make sure the translation integration configuration has content fragment translation enabled.

2. Content Fragment content is present as property main in the crx repo. You would have to add this property in the /content/dam context in translation rules for the content to be translated.

hamidk92094312

Employee

22-08-2019

Please provide the version including the service pack. The reason is to verify if a known issue has been fixed in a certain fix pack so we know if you have the fix in your instance. Also I am assuming the template a an editable template (?)

ashishkhadpe

22-08-2019

Hi Hamid,

Thank you for your quick response.

for translation we are using clay tablet and are able to create different language copies for content fragments.

My concern over here is when I am embedding the en language content fragment in content service page and rolling out that content service page to different locals, other local pages takes the en language content fragment only. Anyway to change reference to point to particular local content fragment?