Asymmetric multilingual configuration: what does it mean that it is not supported?

Created on 13 June 2024, 15 days ago
Updated 20 June 2024, 7 days ago

Problem/Motivation

As stated here https://www.drupal.org/docs/contributed-modules/paragraphs/multilingual-paragraphs-configuration → , translatable paragraph fields on the parent entity .
In the project I'm working on I need to add multiple translations for each node. The page structure of the translation can be different from the original node, hence enabling the translation only on the paragraph fields doesn't suit my needs because the structure of the content cannot be changed for each translation.

I tried enabling the translatable paragraph fields on the parent entity, so I have done the exact opposite of the suggestion in the documentation above and still it works: I can create multiple translations for each node and the structure of the content can differ from the original translation. The content of the page is cloned the first time I click to create a new translation and then I can change the content of the paragraphs items and/or remove, add or rearrange the paragraph items.

I would like to have a better understanding of why the documentation says that this asymmetric feature is not supported when in practice, it seems to work.
Also, I don't understand the warning:
Never enable translation on the Paragraphs field (Entity reference revisions), as it will enable adding new paragraphs while translating, even if an empty field (not containing any paragraph field) is on the translation source node - which is not supported!
I don't see these "new added paragraphs" while translating.

I know that this is the Layout Paragraph issue queue, in fact I'm using this module on top of Paragraphs to build the page content.

I hope you can help me.
Thank you so much

💬 Support request
Status

Active

Version

2.0

Component

Documentation

Created by

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.

Production build 0.69.0 2024