2 results found

1. Retain versions correctly for a content move in CMS tree (to fix invalid editor history

   As a content editor I want to be able to move content (for example a page in the CMS tree. When I do this at present a new version is created but this is merged with the previous update for that content. I want a new version to be created and the old version to be retained in order that the true date/time and editor of any changes is visible from the version history.
   For example:
   * Editor A creates and publishes a page on 1 Sept 2024
   * Editor B updates and publishes the same page on 15 Oct 2024
   * Result (as expected - Version history shows the 2 versions:
   1 Sept 2024 - Previously published by Editor A
   15 Oct 2024 - Published by Editor B
   * Editor C moves the page on 2 Jan 2025 in the content tree (which will update/save the page metadata as the sort ID will change
   * Current result - Version history only shows 2 versions, losing the version from October:
   1 Sept 2024 - Previously published by Editor A
   2 Jan 2025 - Published by Editor C
   Comparing versions it now looks like Editor C has made all the changes on 2 Jan 2025 which were in fact made by Editor B on 15 Oct 2024. The lack of traceability is a significant issue for our customer.
   * Requested result - Version history should show 3 versions
   1 Sept 2024 - Previously published by Editor A
   15 Oct 2024 - Previously published by Editor B
   2 Jan 2025 - Published by Editor C
   Note for Optimizely - We raised this as a bug in ticket 1584615, you have had internal discussions based upon this.

   As a content editor I want to be able to move content (for example a page in the CMS tree. When I do this at present a new version is created but this is merged with the previous update for that content. I want a new version to be created and the old version to be retained in order that the true date/time and editor of any changes is visible from the version history.
   For example:
   * Editor A creates and publishes a page on 1 Sept 2024
   * Editor B updates and publishes the same page on 15 Oct… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Research & Design  ·  0 comments  ·  Versions  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Prevent version history comments from being deleted/archived.

   Currently page comments are removed during the change log truncation process. These comments are associated to the version history and can be used to provide valuable information regarding each content change.
   Our content authors rely on these comments for content audits and other reviews. Ideally these should be maintained as long as the version associated with the comment. Perhaps the retention period could be configurable depending on the site needs.

   11 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Research & Design  ·  0 comments  ·  Versions  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating