Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-13199

Every CONTENT change to the unpublished variant of an Experience Page should result in a new version

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • None
    • None

    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

      Attachments

        Issue Links

          is cloned by

          New Feature - A new feature of the product, which has yet to be developed. CMS-13237 Support EXPLICIT version creation of Experience Page in Channel Manager

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. CMS-13359 [backport 14.x] Every CONTENT change to the unpublished variant of an Experience Page should result in a new version

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Closed

          Task - A task that needs to be done. CMS-13386 [est] Every CONTENT change to the unpublished variant of an Experience Page should result in a new version

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Closed
          relates to

          Task - A task that needs to be done. CMS-13321 Take hippostd:skipDraft into account when diffing variants

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Closed

          Task - A task that needs to be done. CMS-13382 Add auditTrace mixin to experience page

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Closed

          Activity

            People

              ntrajkovski Nikola Trajkovski
              aschrijvers Ard Schrijvers
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: