Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-24991

The position of added fieldtypes are set to zero when editing a content type

    Details

      Description

      Steps to reproduce

      *Create one content type
      *Add two or three fieldtypes as will
      *Notice that the "Position" of the new fieldtypes is always set to "0" (zero)
      *Publish the content type
      *Edit the content type again
      The "Position" of the new fieldtypes are still set to "0" (zero)

      Note: Is we set one of the positions to "1" or "2", publish it, then the position is honored, which is ok.

        Issue Links

          Activity

          Hide
          Gunnstein Lye added a comment -

          (Changed title and description to reflect that only newly added fieldtypes are affected. Existing priorities are not reset to 0.)

          Show
          Gunnstein Lye added a comment - (Changed title and description to reflect that only newly added fieldtypes are affected. Existing priorities are not reset to 0.)
          Hide
          Gunnstein Lye added a comment -

          Paulo Nunes What would you say is the correct behaviour?
          Do you agree this is a duplicate of https://jira.ez.no/browse/EZP-24569 ?

          Show
          Gunnstein Lye added a comment - Paulo Nunes What would you say is the correct behaviour? Do you agree this is a duplicate of https://jira.ez.no/browse/EZP-24569 ?
          Hide
          Paulo Nunes (Inactive) added a comment -

          Gunnstein Lye: I expected the behavior to be the same as in legacy i.e, when I add a new fieldtype, the position number would be set to previous biggest position number + 1, unless the fieldposition is set manually

          Regarding EZP-24569, if the need to be computed correctly__ referred by [~jerome.vieilledent@ez.no] is the expected behavior i referred above, then yes, i guess it's duplicated.

          Show
          Paulo Nunes (Inactive) added a comment - Gunnstein Lye : I expected the behavior to be the same as in legacy i.e, when I add a new fieldtype, the position number would be set to previous biggest position number + 1, unless the fieldposition is set manually Regarding EZP-24569 , if the need to be computed correctly __ referred by [~jerome.vieilledent@ez.no] is the expected behavior i referred above, then yes, i guess it's duplicated.
          Hide
          Gunnstein Lye added a comment -

          Yep, I'm working on that assumption (biggest + 1).

          Show
          Gunnstein Lye added a comment - Yep, I'm working on that assumption (biggest + 1).
          Hide
          Jérôme Vieilledent (Inactive) added a comment -

          Hi

          Position calculation was decided to be a follow-up by ~damien.pobel@ez.no and me, as part of the future "rich" contentType edition

          Show
          Jérôme Vieilledent (Inactive) added a comment - Hi Position calculation was decided to be a follow-up by ~damien.pobel@ez.no and me, as part of the future "rich" contentType edition
          Hide
          Gunnstein Lye added a comment -

          [~jerome.vieilledent@ez.no] Meaning... you don't like the fix for https://jira.ez.no/browse/EZP-24569: https://github.com/ezsystems/repository-forms/pull/55 ?
          This doesn't do client side calculation, I figured that could wait until rich edition (where I guess we will want drag-and-drop positioning).

          Show
          Gunnstein Lye added a comment - [~jerome.vieilledent@ez.no] Meaning... you don't like the fix for https://jira.ez.no/browse/EZP-24569: https://github.com/ezsystems/repository-forms/pull/55 ? This doesn't do client side calculation, I figured that could wait until rich edition (where I guess we will want drag-and-drop positioning).

            People

            • Assignee:
              Unassigned
              Reporter:
              Paulo Nunes (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: