-
Bug
-
Resolution: Fixed
-
Neutral
-
3.0.1
-
None
-
None
Feedback from the customer:
We've debugged the procedure and we noticed that when the source document is generated the transatable i18n fields are searched under the submitted node and not under the Multivalue or Composite node (which are under the submitted node) in our case and that's why the trans-unit element tags not exists in the source document.
Acceptance criteria
- is cloned by
-
EXCONTRANS-335 Multivalue and Composite fields fail when using different transformers v2.9
- Closed
- relates to
-
EXCONTRANS-412 Composite/multiJcrBlocks Fields Fail When Processing Translations
- Closed