[MGNLCTS-109] No export of MultiValueFields Created: 05/Aug/19  Updated: 23/Aug/22

Status: Open
Project: Content Translation Support
Component/s: None
Affects Version/s: 2.1.8
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jonathan Ruiz Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File mnetHotspot.yaml     PNG File module-configuration.png    
Issue Links:
Relates
relates to MAGNOLIA-7586 Storing Properties to a file does not... Closed
relates to MGNLCTS-107 Multivalue fields are not exported Closed
relation
is related to MGNLCTS-86 Composite fields don't appear as tran... Closed
is related to MGNLCTS-126 Support for complex fields Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Team: AuthorX

 Description   

No translation will be exported in case of a MultiValueFieldDefinition. Inside this MutliValue we also use a CompositeField. So it is a quite complex structure in JCR.

See attached definition ( mnetHotspot.yaml ) and module configuration ( ).

As a big client want to translate all pages to chinese they want to use this module with the XLS/CSV export/import.

Magnolia 5.5.8 EE Pro


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