Cloning does not always select most recent revision

Created on 3 August 2021, over 3 years ago
Updated 15 August 2023, over 1 year ago

Problem/Motivation

When cloning a node, it ends up with an older revision.

Steps to reproduce

Go to a node view and click on the "Clone" link. The resulting node will have older content from a previous revision instead of content from the most current one.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Needs work

Version

1.14

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States ethomas08 SF Bay Area

Live updates comments and jobs are added and updated live.
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.

  • πŸ‡¨πŸ‡­Switzerland colorfield Lausanne

    Thanks for the patch, adjusted it a bit as it can fail in some translation cases.

    Was working with this case
    - Create a node in English, published state
    - Translate it in French, published state
    - Create a draft (or a non default revision state) from the French version
    - Create a draft from the English version

    But not in this one
    - Create a node in English, published state
    - Create a draft from the English version
    - Create a draft translation in French
    - Clone from the English version β†’ it clones from the published / default revision

    It's not optimal yet as it could miss to clone translations in some cases + we might want to check first if content moderation is enabled for the bundle, so setting back to needs work.

Production build 0.71.5 2024