We are experiencing a serious issue with project functioanlity related to translation after upgrading to AEM 6.4. The "creating project" and "Adding to existing project" from reference panel in touch UI behaviors inconsistently in AEM 6.4, even with out of box we.retail application. The issue is that after language copy from a "us" site to another language sites (e.g., French, German) by creating a multi-language project. After that ( page translated and come back), you cannot reuse existing project (select add to existing project from reference panel ) to re-translate the same pages again after updating these pages in language copy source.
I wonder if you also experienced the same issue. we tried even with out of box we.retail site, the same issue.
thanks in advance.
Are these answers useful? Help other community members by marking useful answers as accepted.
I checked the "/content/we-retail/language-masters/en/jcr:content", it doesn't have the jcr:language property. Looks like you are very knowledgeable, can you give us the clear instruction on this? thanks.
Try the following steps with out of box setup & We.retail application with default MS translation engine (6.4 + SP2):
From "/content/we-retail/language-master/en", pick couple of pages to do language copy to ther language sites, e.g. FR & DE. Note that, you have two ways to create language copy: a). from AEM console, use "create" dropdown menu; b) from reference panel, use "References" and then "language copy"
Follow through the widget, for translation project selection, please choose "create a multi-language project", then follow through the widget to finish the step.
Go to the project that you created in step 2, manually start the job and finish the translation jobs. translated pages will be back.
Now, modify some above pages, and triger the translation again from "references" panel, and select "add to existing project", select the one from the first translation. now go that project folder, you will notice that:
If you use a) to start the initial language copy, then it will create new project and NOT reuse the existing project even though you choose add to existing project.
If you use b) to start the intial language copy, then it will create new jobs, which is expected.
However, in both scenarios, the jobs created for second translation are not right: job target language is the "US" and NOT "FR" and "DE". Basically, you cannot re-translate the pages again using existing project.
BTW, do you have customers already on 6.4 and using project translation?