Problem/Motivation

--- !!! I am not talking about asynchronus translation !!!---

If the paragraph field is set as not translatable and Hide non translatable fields on translation forms is not checked then we could expect to edit the paragraph in any language:
-deleting an item in french will lead to a deleted item in all languages
-moving an item in dutch will lead to a moved item in all languages
-idem for adding an item
-Editing is already working in all languages

This is the way the other fields are working, this is why I tag this issue as a bug

Steps to reproduce

1-Create a paragraph field
2-Set it as non translatable
3-Uncheck Hide non translatable fields on translation forms for the content type of the field
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

CommentFileSizeAuthor
#5 Crear traducción Español de Testing _ Drush Site-Install.png649.31 KBjjose.quevedo
#5 Edit Test Testing _ Drush Site-Install.png568.69 KBjjose.quevedo
#5 Content language _ Drush Site-Install (1).png229.26 KBjjose.quevedo
#3 Crear traducción Español de Basic page _ Drush Site-Install.png446.1 KBjjose.quevedo
#3 Content language _ Drush Site-Install.png532.52 KBjjose.quevedo

Comments

DuneBL created an issue. See original summary.

dunebl’s picture

dunebl
Primary language French
commented
Issue summary: View changes
jjose.quevedo’s picture

jjose.quevedo commented
Assigned: Unassigned » jjose.quevedo
Status: Active » Closed (cannot reproduce)
StatusFileSize
new Content language _ Drush Site-Install.png532.52 KB
new Crear traducción Español de Basic page _ Drush Site-Install.png446.1 KB

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
    Screenshot 1
  • The field don't appear in the translation of node
    Screenshot 2
dunebl’s picture

dunebl
Primary language French
commented
Status: Closed (cannot reproduce) » Active

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: inside my_node_type) using only my_parag_type as paragraph type
2-Set my_parag_type as non translatable in admin/config/regional/content-language
3-Uncheck Hide non translatable fields on translation forms for my_node_type in admin/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 type my_parag_type

jjose.quevedo’s picture

jjose.quevedo commented
Status: Active » Needs review
StatusFileSize
new Content language _ Drush Site-Install (1).png229.26 KB
new Edit Test Testing _ Drush Site-Install.png568.69 KB
new Crear traducción Español de Testing _ Drush Site-Install.png649.31 KB

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
    Screenshot 2
  • This is the original node
    Screenshot 1
  • This is the translation form of the previous node
    Screenshot 3

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.

dunebl’s picture

dunebl
Primary language French
commented

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 if Hide non translatable fields on translation forms is unchecked

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Needs review » Closed (won't fix)

> 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.

dunebl’s picture

dunebl
Primary language French
commented
Category: Bug report » Feature request
Status: Closed (won't fix) » Active

>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

thomaswalther’s picture

thomaswalther commented

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.

dunebl’s picture

dunebl
Primary language French
commented

@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?

emb03’s picture

emb03 commented

@DuneBL wondering the same, reluctant to add a contrib module to enable this functionality on translated paragraphs.

meryem dibe’s picture

meryem dibe
She/Her
Primary language English
commented

Hello, any updates on this issue ?

yonailo’s picture

yonailo
He/him
commented

In my case I just wanted to reorder the paragraphs of a translation to be different from the order of the original language.

I have installed the module paragraphs_asymmetric_translation_widgets to cope with this.