Changing the language on the default translation results in a 404

Created on 28 February 2023, almost 2 years ago
Updated 23 July 2024, 4 months ago

Problem/Motivation

This is a followup from 🐛 Changing language of the default translation in a draft breaks edit Closed: outdated .

Changing the language on the default translation results in a 404.

Steps to reproduce

  1. Standard install, in English
  2. Enable content_translation, content_moderation
  3. Add two languages, DE and FR.
  4. Enable translation for article
  5. Create article node in EN, published
  6. Add translation in DE, published.
  7. Edit EN, change language to FR, draft.
  8. The user is forwarded to en/node/X/1, which is an access denied.

Proposed resolution

TBA

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

🐛 Bug report
Status

Active

Version

11.0 🔥

Component
Entity 

Last updated about 1 hour ago

Created by

🇳🇿New Zealand quietone

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.

  • Issue created by @quietone
  • 🇮🇳India vinmayiswamy

    Hi, I've been trying to reproduce the issue described here but have not been able to.

    Here are the steps I followed:

    Initial Setup:
    * Standard Drupal 11.x install with English as the default language.
    * Enabled the content_translation and content_moderation modules.
    * Added two additional languages (German and French).
    * Enabled translation for the Article content type.

    Steps Followed:
    * Created an Article node in English and published it.
    * Added a German translation and published it.
    * Edited the English version, changed its language to French, and saved it as a draft.
    * Attempted to access the draft version in French.

    Outcome:
    * I did not encounter the 404 error as described. The draft saved and accessed correctly.

    Request for Guidance:
    * Is it possible that this issue has been resolved in any recent updates?
    * Are there any specific configurations or additional steps that I might have missed?
    * If possible, could someone else attempt to reproduce the issue with the same steps to confirm the outcome?

    Any assistance or insights you could provide would be greatly appreciated.

    Thanks!

Production build 0.71.5 2024