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

DOC: Best practice for renaming pages after publication

XMLWordPrintable

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

      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 rename operation. Best practice from an SEO perspective is to redirect to the new location. Therefore, a published page cannot simply be renamed. 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, renaming a node is the same thing as creating a new node.

      The steps should be:

      • Copy the source node.
      • Change its name.
      • Redirect the old page to the new page.

      Notes
      Renaming a page also affects all child pages due to URL rewrites

        Acceptance criteria

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

                Created:
                Updated:
                Resolved:

                  Task DoD