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

pageIterator does not correctly replace the "current" node after it finishes looping

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • 4.3.1, 4.2.4
    • taglibs
    • None

    Description

      pageIterator relies on info.magnolia.cms.taglibs.Resource.restoreCurrentActivePage() to restore the current node after execution. However, restoreCurrentActivePage() simply assumes that you wish to set getMainContent() as the current node. It seems more friendly to save off the current content node before execution, and restore it afterwards.

      The included patch does exactly that. File to be patched is magnolia-taglib-cms/.../pageIterator.java.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              nwing Nickolaus Wing
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Bug DoR
                  Task DoD