[EXCONTRANS-371] XliffTransporter - Recursive Export for Content Apps Created: 20/Apr/22  Updated: 04/May/22  Resolved: 03/May/22

Status: Resolved
Project: Content Translation Extended (CTX)
Component/s: Core
Affects Version/s: 3.4.4
Fix Version/s: 3.4.5

Type: Support Request Priority: High
Reporter: Florian Kugler Assignee: Teresa Miyar
Resolution: Fixed Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia 6.2.17


Attachments: Zip Archive Products-ContentApp-Sample.zip    
Template:
Date of First Response:

 Description   

Hello all, 

when creating TranslationBatches for Content-Apps and checking 'Include Subnodes' the created Batch recursively includes all relevant i18n Fields (equivalent behavior to Pages-App).

But the document created for TranslationSubmission currently uses 'XliffTransporterImpl#doExportForApp' which then calls protected '#export' once and only includes i18n Fields for the current node. After that '#isProcessed' compares 'path' and 'configPath' properties and therefore skips all other i18n Fields that have been initially added for the TranslationSubmission (since they all match those properties but have different values in 'link' property). 

The resulting sourceDocument only contains i18n fields of the parent Node but not its child nodes although all relevant i18n fields are available in the TranslationSubmission Object. 

Is this current behavior intentional and if so is there any other way to properly use 'Include Subnodes' for Content Apps as well? 

Thanks in advance and best regards, 
Florian



 Comments   
Comment by Riste Drangovski [ 20/Apr/22 ]

Hi Florian,
I tried to reproduce the issue you are facing, but without luck.
Can you please attach the content-app definition file (yaml) to this ticket.
I can try to use your content app, so hopefully that way I can reproduce the issue and pinpoint the problem ...

Comment by Florian Kugler [ 21/Apr/22 ]

Hi Riste, 

i attached the custom ContentApp where the Export Problem occurred first, included you will find the YAML as well as nodetypes.xml and some Sample Content exported from JCR. 

For the Sample Content: if you add 'Sample-Product' to Translation Batch with 'Incl. Subnodes' checked, i18n Fields of the Sample-Product,  both Sample-Variants and their respective Attributes should appear within TranslationSubmission (We registered Switchable-Fields, Composite-Fields, MultiValue-Fields as well as Text- and RichText-Fields for the Translation Adapter; In Multisite our MasterContent i18n-Config has 'en' as Fallback and translation source and registered about 40 other locales including 'de_DE' that can be used as translation targets). 

If you need anything else let me know!

Best regards, 
Florian

Comment by Florian Kugler [ 02/May/22 ]

Hi all, 

do you have any new information regarding this topic as of now?

Thanks, 
Florian

Comment by Teresa Miyar [ 03/May/22 ]

Hi,

We are about to merge a fix, it was a complex scenario since you had nested content types in the app, something that was not supported, we will provide a new release by the end of the day.

Regards,

Teresa

Comment by Teresa Miyar [ 03/May/22 ]

Hi,

New version 3.4.5 available with the fix for this problem.

Comment by Florian Kugler [ 04/May/22 ]

Hi Teresa,

thank you very much! 

Best regards, 
Florian

Generated at Mon Feb 12 00:30:35 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.