aem-guides-wknd icon indicating copy to clipboard operation
aem-guides-wknd copied to clipboard

Published 20 hours ago • verified publisher icon adobe

Issue with XF TRANSLATION

Open digarg opened this issue 3 years ago • 2 comments

Expected Behaviour Experience fragment 'X' is created under /wknd/us/en/X is referenced on a wknd page using content page template . This page is subjected to ootb translation to es language. It should create Experience fragment 'Y' automatically upon translation under /wknd/us/es and also update XF link on wknd page in 'es' language .

Actual BehaviourExperience fragment 'X' is created under /wknd/us/en/X is referenced on a wknd page using content page template . This page is subjected to ootb translation to es language. It does not create Experience fragment 'Y' automatically upon translation under /wknd/us/es and also XF link on wknd page in 'es' language still refers to XF under /en.

Reproduce Scenario (including but not limited to) This works fine if I use We retail template rather than wknd content page to create pages under we.retail site and refer XF under weretail or wknd site.

Steps to Reproduce

  1. Create XF under /content/experience-fragments/wknd/us/en/X.
  2. Create a page under /content//wknd/us/en/Y
  3. Drop an XF core component and provide reference link of XF created in step 1.
  4. Translate the page created in step 2 via OOTB translation process. I used references ->language copy -> create translation project ->select language es -> start translation project .
  5. Once translation completes, check if an XF gets automatically created under /content/experience-fragments/wknd/us/es/. This is not happening .
  6. check on page if XF link is updated to refer XF under 'es' instead of 'en' This is also not happening.

Platform and Version - AEM 6.5.9

Sample Code that illustrates the problem - wknd reference site - aem-guides-wknd.all-1.0.0-classic

Logs taken while reproducing problem

error.log

digarg avatar Jun 29 '21 17:06 digarg

@digarg thanks for reporting! Do you have any sense of why this is not happening n the project? have you been able to verify this works on 6.5.9 for other projects (ie. is it a problem with WKND itself, or possibly a product issue?)

davidjgonzalez avatar Aug 05 '21 20:08 davidjgonzalez

Checked internally, looks like this was fixed in 6.5.10. Can you check again?

keepthebyte avatar Nov 12 '21 01:11 keepthebyte