Details
-
Improvement
-
Resolution: Won't Do
-
Neutral
-
None
-
6.2
-
None
-
None
-
-
Empty show more show less
-
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.
Notes
Renaming a page also affects all child pages due to URL rewrites
Checklists
Attachments
Issue Links
- is related to
-
MAGNOLIA-8053 Copying JCR items should strip activation and modification metadata
-
- Closed
-
-
MTE-115 MTK should provide a redirect page template
-
- Closed
-
-
MTE-126 Best practice actions for public facing workspaces
-
- Closed
-
-
PUBLISHING-188 Publishing children of a renamed parent throws exception
-
- Closed
-
-
PAGES-357 DOC: Best practice for moving pages after publication
-
- Closed
-
- links to