Clean-up version history

[ulliholtgrave]

Motivation

If users are editing a single page for a couple of hours a lot of automatic saves are created which results in a very crowded versioning view and a lot of unnecessary database objects.

Proposed Solution

If the user triggers a manual save delete all automatic translations for this specific translations, but keep the latest 3 as a safeguard. (this is not wished anymore as of May 2024)
instead:

• Only keep auto saves since the last manual save
  • Autosave field: translation.status == constants.status.AUTO_SAVE
• Clean up of the current history
  • Past autosaves cannot be identified by the status field, thus:
    • We compare version to each immediate version whether they have the same content and only keep the newest version where we can't count on the auto save status to be accurate
    • Infer autosaves, which means: Delete all versions that are only one minute (+/- tolerance) apart because manual saves wouldn't happen in that speed
  • Write database migration to delete all versions we identified as auto saves

Alternatives

Adapt the view to only show a few automatic translations?

Additional Context

Design Requirements

[timobrembeck]

Important note: We expect the version history to be consistent in several places of the CMS, so you would have to squash the version numbers to make sure there are no gaps.

[PeterNerlich]

We have probably identified a bug in the current logic: When saving a translation version as Draft or Published (if it is a minor edit), all versions of the translation (for Draft even all of the descendant languages in the language tree) are set to Draft/Published. We expect that only the status of the most recent version in each language is supposed to be updated.

If we get confirmation that this is the intended effect, we could cover this in our PR since we are already touching that code.

Edit: Summary from the team call: This emerged for historic reasons, the intention is for previously published versions to be reduced to Draft as well if the current translation is saved as Draft. We will adjust the queries to only affect published versions, keeping auto saves and versions with other status as they are.