- Issue created by @DuneBL
- Assigned to jjose.quevedo
- Status changed to Closed: cannot reproduce
over 1 year ago 9:10pm 25 July 2023 - πΊπΎUruguay jjose.quevedo
Hi, I was trying to reproduce this issue, but I couldn't. It seems everything is working properly using vanilla Drupal. Here are some screenshots:
-
One field was hidden in the translation configuration
-
The field don't appear in the translation of node
-
One field was hidden in the translation configuration
- Status changed to Active
over 1 year ago 7:07am 26 July 2023 - π§πͺBelgium DuneBL
Sorry, I think I was not clear enough because it is not the case I was talking about. Here are the steps with more explainations:
1-Create a paragraph field inside a content type (ex: insidemy_node_type
) using onlymy_parag_type
as paragraph type
2-Setmy_parag_type
as non translatable inadmin/config/regional/content-language
3-UncheckHide non translatable fields on translation forms
formy_node_type
inadmin/config/regional/content-language
4-Create a node and translate it
5-Go to the translated node, you will not be able to add, delete or move a paragraph item of typemy_parag_type
- Status changed to Needs review
over 1 year ago 6:30pm 26 July 2023 - πΊπΎUruguay jjose.quevedo
Thank you for providing the clarification. I attempted to reproduce the issue again, but I couldn't observe any problems using vanilla Drupal. I followed the steps you outlined, and I'm sharing the screenshots for your reference:
-
This is the configuration
-
This is the original node
-
This is the translation form of the previous node
As you can see, the paragraph can't be added, deleted, or moved in the translated node. So, if there is anything specific you would like me to try or if you have any additional information, please let me know.
-
This is the configuration
- π§πͺBelgium DuneBL
As you can see, the paragraph can't be added, deleted, or moved in the translated node.
This is specifically the object of this bug: there is no reason to avoid the addition/deletion or move of the paragraph items.
Let explain this with another field type:
For exemple, if you have a multivalue field which is not a paragraph and if this field have the same settings:- not translatable
- and the parent node have
Hide non translatable fields on translation forms
unchecked.
Then, in the translated node form, you can add/delete/move the items of this field... If this is a paragraph field you can't.
This is what a user is expecting: being able to manipulate non translatable fields in all languages ifHide non translatable fields on translation forms
is unchecked - Status changed to Closed: won't fix
over 1 year ago 10:13pm 30 August 2023 - π¨πSwitzerland berdir Switzerland
> This is specifically the object of this bug: there is no reason to avoid the addition/deletion or move of the paragraph items.
Drupal does not allow to change multiple translations at once and that's exactly what would happen. This is not a bug, this is by design and will and can not be changed.
- Status changed to Active
over 1 year ago 9:59am 31 August 2023 - π§πͺBelgium DuneBL
>Drupal does not allow to change multiple translations at once and that's exactly what would happen. This is not a bug, this is by design and will and can not be changed.
I don't follow you because:
- The field is not translatable
- This can be done with another field type: like a (not translatable) multivalue text field
I changed the category into feature request
- π©πͺGermany thomaswalther Rhein-Main Area
A translated node with paragraphs only should be able to edit/translate like a translator would do.
Changing the order or delete/add one item should ONLY be done from/with the original node (Original language)After adding/deleting/moving a paragraph from the original language node, then the translator must visit the other translation (with the not yet setted translated values) and should have the fallback field and could now update this field for this language.
Otherwise, a translator would be able to delete/update/move the paragraphs, that's not the work of a translator.
- π§πͺBelgium DuneBL
@thomaswalther I am talking about not translatable paragraphs. Which should not be edited by translators.
We can compare this paragraph field with any other not translatable multi-value fields. A not translatable multi value field can be re-ordered in the translated node, we can also add/delete a value. This is the regular Drupal's behavior.
Why the not translatable paragraph fields does not follow the same rules?
- πΊπΈUnited States emb03
@DuneBL wondering the same, reluctant to add a contrib module to enable this functionality on translated paragraphs.