Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-6274

Multivalue field is not displayed correctly if number nodes are not correlative

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Neutral Neutral
    • None
    • 6.2.3
    • None
    • None

      Dialogs that contains a multivalue field is not displaying correctly the Multivalue field values if nodes are not correlative. It is not detected that there is a missing node and it is displayed in the dialog as an empty entry.

      Steps to reproduce

      1. create a new dialog definition (see dialog definition attach)
      2. Open the dialog and include for entries using the multi value field.
      3. Go to JCR Browser and delete one of them in the middle
      4. Open the dialog again to see the current data

      Expected result

      Just the existing nodes are displayed

      Current result

      The deleted node is displayed in the dialog with missing values. The last node with content is not displayed.

      Workaround

      There is a groovy script that is fixing this nodes, this script has been created by the partner (Big Thanks!)

      Dev notes

      In Magnolia 5.7 this issue didn't happen, the deleted node is ignored and not displayed.
      If the entry is removed from the dialog itself, the nodes are renumbered in the correct order.

      Same issue is happeningg on 6.2.3 with the new UI 6 definition

      form:
        properties: 
          itemsLex:
            $type: jcrMultiField
            itemProvider:
              $type: jcrChildNodeProvider
              supportI18N: false
            entryResolution:
              class: info.magnolia.ui.editor.ByLexicographicallyIndexedChildNodes$Definition
            orderHandler:
              class: info.magnolia.ui.editor.LexicographicallyIndexedJcrNodeOrderHandler$Definition
            field:
              $type: compositeField
              properties:
                text:
                  $type: textField
                link:
                  $type: textField
      

        Acceptance criteria

              sdemocko Šimon Demočko
              miruela Mercedes Iruela
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD