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 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
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
-
-
PAGES-358 DOC: Best practice for renaming pages after publication
-
- Closed
-
-
MTE-126 Best practice actions for public facing workspaces
-
- Closed
-
-
MGNLSYNC-51 Synchronisation may fail when nodes are moved into different sub trees
-
- Closed
-
- links to