[MGNLCTS-93] Nested composite fields are not exported Created: 06/Mar/18  Updated: 02/Dec/22  Resolved: 02/Dec/22

Status: Closed
Project: Content Translation Support
Component/s: None
Affects Version/s: 2.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Jonathan Ayala Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: maintenance, to-verify
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
relation
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:
Epic Link: AuthorX Support
Team: AuthorX

 Description   

When there's a composite field with a nested composite field in one of its fields, its value is not exported.

 

Steps to reproduce:

  1. Create a composite field
  2. Add another composite field as one of the fields of the composite field created in stem 1
  3. Add i18n=true to the fields in each composite field
  4. Use this dialog to create a new page and export it using content translation support app

Result: fields of nested composite field don't appear in the exported file



 Comments   
Comment by Laura Delnevo [ 02/Dec/22 ]

Hello, 

This ticket is now marked as closed due to one of the following reasons: 

  • A long period of inactivity 
  • Uses an old or Beta version of an application, module, or framework that we no longer support 
  • The issue is no longer reproducible or has been fixed in later versions 

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you. 

Thank you, 

The Magnolia Team

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