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

DOC: Best practice for moving pages after publication

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Won't Do
    • Neutral
    • None
    • 6.2
    • None
    • None
    • Yes

    Description

      A page node can have many different states. Versioned/Not versioned. Published/Not published. Modified/Current.

      After a page has been published we should consider disabling the move operation. Best practice from an SEO perspective is to redirect to the new location. Therefore, a published page cannot simply be moved. It needs to be "deprecated" with a redirect template to its new location. The new node should be a copy of the old node and disconnected from the the version history. In simple terms, moving to a new location is like stating a new life.

      We could consider creating a "mgnl:copiedFrom" metadata which contains the uuid of the original node.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                rgange Richard Gange
                rgange Richard Gange
                Votes:
                1 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoD