Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-3361

versioning: ContenVerstion.getContent(), hasContent() and getChildren() are not all working as they should

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • 4.3.9, 4.4
    • 4.3.8
    • core
    • None

    Description

      getContent(), hasContent() and the getChildren() variations are not following the same principles. They should return direct children if they were included in the version rule and children of the current node if they are no matched by the version rule.

      The idea of VersionContent is supposed to hide the fact that it resides in the version store.

      Example: A page version includes all sub paragraphs but not the sub pages. If you read a paragraph it should only return direct children, if you read sub pages it should only use the current node.

      The actual situation is:

      • getContent() and hasContent() only return direct Children
      • getChildren() works as expected but the method getChildren(filter, pattern, comp) is not implemented so as soon the node gets wrapped the getChildren() methods return different entries.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                pbaerfuss Philipp Bärfuss
                pbaerfuss Philipp Bärfuss
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Bug DoR
                    Task DoD