SOLVED
Should rollout to live copies be done first then en-us content should be submitted for translation?
Looking for best adobe practices and recommendations.
1. We have pages in en-us with the live copies maintained in locales eg es-es.
2. We add a component in en-us and do the rollout which makes the component available in the live copy locale es-es with cq:LiveRelationship property.
3. We submit the en-us content for translation and translation brings back the translated content to the live copy locale es-es with keeping the cq:LiveRelationship property intact. Everything goes well.
but we have an issue in above step #2 when we dont rollout the en-us first so the new component does not exist in the live copy and no cq:LiveRelationShip property and directly submit the content for translation. In this case, content is translated but the cq:LiveRelationship property does not exists.
In this case if a user does the rollout from en-us then because there is no live relationship for the components, it moves the existing translated component to component_msm_moved node and copies the component from en-us to the live copy with cq:LiveRelationship.
Checking what should be the best practice so that we can implement the change or advise authors on what to do?
1. Should they always be doing the rollout first before submitting for translation
2. When translation comes back should be trigger a workflow and establish the relationship
3. Should we prevent content translation by checking if rollout needs to be performed.
1 Accepted Solution
Correct answer by
@vsharm you can have a workflow which will first rollout the pages and then submit it for translations right. So content authors will trigger the workflow only.
Correct answer by
@vsharm you can have a workflow which will first rollout the pages and then submit it for translations right. So content authors will trigger the workflow only.
