Details
-
New Feature
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
1
-
Quasar
-
Puma Sprint 233, Puma Sprint 235
Description
For experience pages, make sure that every save to the preview for content results in a new version (not every change to the layout which also ends up in the preview)
Note that this thus works differently than for normal documents, which in general only on publication (apart from branching) results in a new version! For experience pages, saving the draft to unpublished should directly trigger the creation of a new version (which can be restored / viewed) later
Howto
Not sure if this is the best approach, but what we could do is introduce a new mixin in the hippostdpubwf (or hippostd or hippo) namespace, for example
hippostdpubwf:versionpreviewchange
when this mixin is on a document variant or on the handle, the document workflow scxml should create a new version on any change 'commiteditable instance'
NOTE
If this is implemented by changing SCXML, then make a separate backport issue for 14.x since we should not modify scxml in 14.x