[MGNLUI-4052] Nesting composite and multivaluefields gives issues for multilingual saving Created: 24/Oct/16  Updated: 30/Sep/21  Resolved: 30/Sep/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Pieter Ardinois Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: composite, dialog, fields, multivalue, y2k
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 14.04, Ubuntu 16.04


Attachments: HTML File extralinks_config    
Issue Links:
relation
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:

 Description   

We have a page where we have nested multivalue and composite fields multiple times in the property dialog.
I will add the configuration as an attachement extralinks_config.

These are the steps where i get the issue:

  • I switch my page language to an other that it not the primary language.
  • I open the edit dialog for the page
  • switch to an other language and then switch back to the previous one.
  • edit a value in the composite field
  • click save changes.

Now the changes are not saved. This issue only occurs when I swich languages. if I edit and save the data does get saved.



 Comments   
Comment by Roman Kovařík [ 08/Mar/21 ]

mdivilek Could you check if this is still an issue in the new framework?

Comment by Milan Divilek [ 19/Aug/21 ]

rkovarikjsimak I did few tests:
1. Magnolia 5.4.9 - I was able to reproduce the issue with definition provided by Ervin
2. Magnolia 5.7.12-SNAPSHOT - I was unable to reproduce the issue with definition provided by Ervin in old framework anymore
3. Magnolia 6.2.12-SNAPSHOT - I was unable to reproduce the issue in new framework

form:
  properties:
    multi:
      label: multi
      $type: jcrMultiField
      field:
        $type: compositeField
        properties:
          text:
            label: text
            i18n: true
            $type: textField
          multi:
            label: multi2
            $type: jcrMultiField
            field:
              $type: compositeField
              properties:
                text2:
                  label: text2
                  i18n: true
                  $type: textField
                text3:
                  label: text3
                  i18n: true
                  $type: textField
          
  layout:
    $type: tabbedLayout
    tabs:
      - name: tabMain
        fields:
          - name: multi
Comment by Marta Kobus [ 30/Sep/21 ]

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 09:12:46 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.