Non-default entity revisions are migrated as default revision because EntityContentComplete does not allows creating forward (and non-default) revisions

Created on 1 March 2021, over 4 years ago
Updated 23 May 2025, 16 days ago

Problem/Motivation

Identified while working on Bean Migrate β†’ :

The EntityContentComplete migration destination plugin blindly marks every migrated content entity revision as default revision. This is wrong, because a moderated entity might have forward (so not-yet-default or not-yet-published) revisions as well.

Proposed resolution

Check whether the row being migrated has a revision_default destination property.

  • If the property's value is FALSE, do not set default revision.
  • If the property is not set at all, or its value is NULL, or it has a value, mark the entity revision as default revision.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

πŸ› Bug report
Status

Postponed

Version

11.0 πŸ”₯

Component

migration system

Created by

πŸ‡­πŸ‡ΊHungary huzooka Hungary πŸ‡­πŸ‡ΊπŸ‡ͺπŸ‡Ί

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024