Uploaded image for project: 'Magnolia pages module'
  1. Magnolia pages module
  2. PAGES-96

Magnolia saves the "position" attribute to newly added component

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Neutral
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.4.9, 5.5.1
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Kromeriz 71
    • Story Points:
      3
    • Magnolia Release:
      5.4.10, 5.5.1

      Description

      When adding a new component, magnolia asks if the component should added at top or at bottom of the area.

      If the dialog has a field (e.g. Text Field) with the name «position», it gets filled with either «top» or «bottom».

      If the field is a select field with the values

      • left (selected)
      • right
        no value is selected when creating a new component, due the value of «position» is already set to «top» or «bottom». This behaviour leaded to many problems in our projects.

      This value get also stored to the component, which makes absolutely no sense, due the component may be moved afterward.

      Tested on demoauthor

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jsimak Jaroslav Simak
              Reporter:
              tomwespi Tom Wespi
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response: