Sub-paragraph fields cannot be translated

Created on 28 March 2017, over 7 years ago
Updated 12 September 2023, about 1 year ago

Drupal 8.2.7
Paragraphs 8.x-1.1

Step to reproduce:

1. Create a paragraph type called "Accordion" with title and body text fields
2. Create a paragraph type called "Accordion group" with a paragraphs field of type "Accordion" and no other fields
3. Create a content type using an "Accordion group" field
4. Create an English node with an Accordion group containing an Accordion. Enter "English" in the title and body.
5. Translate the node to another language, change "English" to "translated".
6. Check the English node.

Expected result:

English node contains "English".

Actual result:

English node contains "translated".

Workaround:

Add a dummy "Dummy to fix translation" text field to the "Accordion group" paragraph type, and enable its translation. You can now translate the fields.

More info:

See thread beginning here, where the workaround comes from: https://www.drupal.org/node/2735121#comment-11925679

🐛 Bug report
Status

Needs work

Version

1.0

Component

Code

Created by

🇫🇮Finland hugovk

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.

  • leymannx Berlin

    Oh Jesus, workaround == life saver!! Found out, it's already enough if you simply select the published field of the parent paragraph bundle to be translatable under /admin/config/regional/content-language.

  • leymannx Berlin

    Shit, the "workaround" introduces another major downer: The first time after the workaround you add a new paragraph item in the original language all original language paragraph items get synced to the translation language again, replacing the translations. After that it's fine. It's just the first time this happens.

Production build 0.71.5 2024