Details
-
Task
-
Resolution: Done
-
Medium
-
None
-
6.0, 6.1, 6.2
-
None
-
None
Description
A client designed a system of offering historic views of terms and conditions pages to customers only to find that the version history of a page node is only stored on the author instance.
They have requested that the documentation make this clearer so nobody repeats their mistake. When publishing an update, the version history (up to the max limit of versions) is retained on the author but no history is retained on the public instances: the existing content is overwritten and the older versions are forgotten about.
Checklists
Acceptance criteria
Attachments
Issue Links
- relates to
-
PAGES-209 Versioning Actions Disabled on Public Instances
-
- Closed
-