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

Best practice for renaming pages after publication

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Neutral
    • Resolution: Unresolved
    • Affects Version/s: 6.2
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Release notes required:
      Yes
    • Documentation update required:
      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 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.

        Checklists

        Acceptance criteria

          Attachments

            Issue Links

              Activity

                People

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

                  Dates

                  Created:
                  Updated:

                    Checklists

                    DoD