- 🇺🇸United States justin2pin
I believe this is a duplicate of 🐛 Async translations do not correctly clone the source paragraph Needs review which includes tests as well addresses the needs to correctly map new paragraph uuids for cloned paragraphs.
The module in general terms works great and provides a better authoring experince IMO.
However, a particular use case where site has content translation enabled and content on multiple languages might prioritize some elements or display a whole set of elements. Paragraphs by default notify that a paragraph field does not suppor translation and instead translation falls down to the fields of the paragraph.
When having a multilanguage site, translations on the layout field copy the same layout as the source node (symmetric) but also show the label This is Translation Context (editing a version not in the original language). No new Layout Sections and Paragraphs can be added.
This makes it, for the moment, impossible to address such use case.
* Follow the guide to setup the Layout Paragraphs module.
* Enable content translation.
* Set translation options for the content type where the layout paragraph field is added.
* Create a node in the source language.
* Add a translation to the node.
* Add this point on the new page you should see the label mentioned earlier.
Not familiar with current implementation, but willing to assist in the development of this feature if provided guidance.
Found this items while doing research:
*
Layout Builder Asymmetric Translation →
*
Paragraphs asymmetric translation widgets →
I have tested with a group of developers, that having Layout Builder Asymmetric Translation works, but the user experience requires a lot of customization which could be reduced if we were to fix this translation issue.
* Add somewhere an option, or identify by context, if a layout will support assymetric translations. If it doesn't, keep current behavior. If it does, use the "new logic".
Closed: duplicate
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I believe this is a duplicate of 🐛 Async translations do not correctly clone the source paragraph Needs review which includes tests as well addresses the needs to correctly map new paragraph uuids for cloned paragraphs.