Adding a new draft translation to a published page breaks edit functionality

Created on 4 March 2024, 10 months ago
Updated 7 June 2024, 7 months ago

Problem/Motivation

Adding a new draft translation to a published page breaks edit.

Steps to reproduce

Standard install (10.2.2), in English
content_translation, content_moderation are enabled.

This affects multiple languages, but here's an example:

  • Create node in EN, published.
  • Add translation in ESP, draft; save this page.
  • Edit ESP draft by choosing the edit button in the translation list.

The result is that /en/node/X/edit works as expected, but clicking the edit button for the translated page in the translation list throws an exception (WSOD).

going to /esp/node/X/ shows only the english page content, not the translated content.

going directly to /esp/node/X/edit throws an exception (WSOD).

going directly to /esp/node/X/latest will show the translated content as expected but still throws an exception (WSOD) if you try to edit the content on that page.

πŸ› Bug report
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component
EntityΒ  β†’

Last updated about 16 hours ago

Created by

πŸ‡ΊπŸ‡ΈUnited States smithkr

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @smithkr
  • πŸ‡¬πŸ‡§United Kingdom aaron.ferris

    Not sure if im missing config of some description, but im not able to recreate this behaviour on a 10.2.3 install

    • Install Drupal 10.2.3
    • Enable content moderation
    • Enable content translation
    • Add a second language (ive configured Welsh)
    • Configure content translation for the basic page content type
    • Add a basic page in English, published
    • Add a translation for Welsh, leave in draft
    • Edit the draft from the content translation overview

    Expected
    No WSOD, the content being edited is the translated content

    Actual
    No WSOD, the content being edited is the Welsh content

    I'll add I did see a similar behaviour to this on a previous Core version (10.1), but no WSOD. Oddly I was seeing the original content language when editing the translated draft, but when viewing the translation it was showing the correct translated content.

    So possibly something thats been fixed in 10.2.3?

  • Status changed to Postponed: needs info 7 months ago
  • πŸ‡ΊπŸ‡ΈUnited States xjm

    Sounds like we need more information here.

    Moving to 11.x, which is where issues get fixed first.

Production build 0.71.5 2024