Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.4.5, 5.5
    • Fix Version/s: 5.4.6, 5.5.3
    • Labels:
      None
    • Sprint:
      Kromeriz 90
    • Story Points:
      2
    • Magnolia Release:
      5.4.12, 5.5.4

      Description

      Wrong nodes order after publishing in multiple nodetypes content app.
      Steps to reproduce:
      Open asset app and create a structure as below:

      Publish it to public instance, then the '0' folder has been dropped to the bottom:

      Thanks to Mariusz Chruscielewski for your provided info:

      In ActivationCommand, method protected List getOrderingInfo(Content node) builds list of siblings in correct order for reordering after publication, but it will work only if siblings are of the same type. As we can have multiple node types in one content app (like I have here), it cause order problem I experienced.
      Please consult somebody if this is expected behaviour, and maybe document it somewhere?
      My workaround was to extend activationCommand class and change this sibling type check, to accept all my custom node types.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ajuran AntonĂ­n Juran
                Reporter:
                viet.nguyen Viet Nguyen
              • Votes:
                2 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: