[EXCONTRANS-332] Translation of text with subnodes executed only for root level - no subnodes Created: 27/Feb/20 Updated: 05/Mar/20 Resolved: 05/Mar/20 |
|
| Status: | Resolved |
| Project: | Content Translation Extended (CTX) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Support Request | Priority: | Neutral |
| Reporter: | Ronald Kerstens | Assignee: | Teresa Miyar |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 3h | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Date of First Response: |
| Description |
|
We have made a Product Documents app which consists of subapps for each (hierarchical) document downloads level defined in the app (Category, Subcategory, Product, Product Variant levels). Now when a content author tries to translate EN language a batch of product documents titles (Example: documents titles on a root Category level) and the document titles in its subnodes (Subcategory, Product and ProductVariant), the translation is executed only for the root level document titles: in this case for document titles on a Category level only. The rest of the document titles in the sublevels are not sent for translation at all if you select the "Include subnodes" option. We suspect this is caused by the subapps architecture of our Product Documentation app, but we are not sure about this. Should the "Include subnodes" option also be working in apps which contain subapps? Is this a bug. or does this feature not support content stored in subapps? If it doe not support such content, can we remove it from the dialog only in case such an app with subapps is used? It seems you can only enable/disable the feature for the dialog as a whole.
|
| Comments |
| Comment by Ronald Kerstens [ 27/Feb/20 ] |
|
Technical clarification by Ljubica: The includeSubnodes option is not working when there are multiple Detail subapps in an APP. We have an APP that supports multiple node types. One node type can be set under another. Each node type has its own Detail subApp. So when the author adds a different item (a different node type) under an existing one a specific subApp Detail is opened with its own i18n fields. When we try to translate a node together with its subnodes, the subnodes fields content is not translated. The reason is that the module is taking only the Detail subApp from the first selected parent node with its i18n fields for generating the Source document. The other subApp Details with their i18n fields are ignored. Hint! The place where the module takes all the i18n items from the subApp detail is in info.magnolia.translation.ext.core.command.ExportTranslationCommand the method name: resolveItems
Hope this helps pinpoint the issue.
|
| Comment by Teresa Miyar [ 28/Feb/20 ] |
|
Hi, I will need some sample data to investigate this issue, can you share that app jcr content, the app configuration and the batch export? If not possible a sample app where you can reproduce the problem? if that is not possible either, maybe we can setup a call? |
| Comment by Teresa Miyar [ 04/Mar/20 ] |
|
Default behaviour is: ../dataA what you have is: ../dataA/dataB One way around this problem is to provide your own implementation of I18nItemResolverImpl in the module descriptor that will handle your custom scenario. <component> |
| Comment by Teresa Miyar [ 05/Mar/20 ] |
|
Suggested solution verified |