Child pages being overwritten in English after root page is translated | Community
Skip to main content
N
nwatson69
Level 2
July 1, 2020
Solved

Child pages being overwritten in English after root page is translated

  • July 1, 2020
  • 2 replies
  • 1861 views

This is the scenario we are facing:

1. Create a translation project with a page and its child pages. All pages are translated, and appear in langauges as expected.

2. Create a new translation project with the same page (because the English page been updated), but do not include child pages (because they are unchanged)

Result:

After the page translation is returned (item 2 above), the underlying child pages are being reset to English on the language site.

We are able to reproduce this issue both in our 3rd party translation connector as well as the in-built Microsoft translation connector 

 

Any idea why this is happening and if there is a way around it? The child pages should be untouched on the langauge site, if only the root page is sent for updated translations

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by raj_mandalapu

it should not happen, I have tested in my local environment and unable to reproduce this issue, can you please let us know what is the AEM version you are using?

The configuration which I have chosen? for scenario selected "Assets/Pages" which include all child pages for scenario 2 "Assets/Pages(without child pages)" 

Used "update language copy option"

Once the project is in "ready for review state" did you check your job on pages list? did you find any child pages in the job?

 

 

2 replies

tatvam
tatvam
Level 2
July 1, 2020

You might want to uncheck isDeep property.

 

This is explained here - https://helpx.adobe.com/experience-manager/6-3/sites/administering/using/tc-rules.html

    N
    nwatson69Author
    Level 2
    July 28, 2020

    we've investigated this further and find it only happens when the AEM translation framework creates a launch

    reproduce this on a Vanilla AEM instance under following conditions:

    1. The page + child pages need to exists in the master language
    2. The page + child pages need to exists in the other language
    3. The cq:modification date (or jcr:modification date) of the master page needs to be > jcr:created date of the page in the other language
    4. Start the project using the create translation project Wizard and make sure that the “Create/Update language copy” is selected
    raj_mandalapu
    raj_mandalapuAccepted solution
    Level 7
    July 2, 2020

    it should not happen, I have tested in my local environment and unable to reproduce this issue, can you please let us know what is the AEM version you are using?

    The configuration which I have chosen? for scenario selected "Assets/Pages" which include all child pages for scenario 2 "Assets/Pages(without child pages)" 

    Used "update language copy option"

    Once the project is in "ready for review state" did you check your job on pages list? did you find any child pages in the job?

     

     

      Terms & ConditionsAccessibility statement

      Loading footer...