Unable to update multiple languages simultaneously

looks like you should be able to change the node language - https://www.drupal.org/node/2993847 but i dont think ive ever tested on a node with multiple languages. ill try to set something up and make a fix when i get a chance. Patches always welcome also

Got the same issue and the same need :)

Here is a first try on that

Here's a second try expanding on that against 9x-beta1, but it still only updates the last translation selected even though it seems like it shouldnt based on https://drupal.stackexchange.com/questions/218833/set-translated-field

I noticed when checking the field arrays that they came out like

[field_name] => Array(
  [x-default] => Array(
    [0] => Array(
      [value] => test1
    )
  )
  [es] => Array(
    [0] => Array(
      [value] => test1
    )
  )
  [fr] => Array(
    [0] => Array(
      [value] => test1
    )
  )
)

but when i tried updating them using

$field_value[$langcode][0]['value'] = 'test1';

instead of

$field_value[0]['value'] = 'test1';

that just updated nothing at all.

Wondering if there is a core bug between bulk updating and the "shallow clones" of translated entities? maybe someone else knows more..

Ok I found where the issue is, I've got a patch to fix it BUT it's not the most optimized way to do it.

In fact when you choose your different translations, let's say 10 langcodes. You put them into the batch as entities but it also sets the value field of all translations with it. So in fact you have 10 times the same entities and values.

When you update your first entity, it really updates the entity. When you get the second entity from the queue, in fact you don't have the good version of your entity, when you will update this "langcode" version, you will also override the previous one with a bad value because the field value in the queue is not good.

To avoid that, I reload the latest version of the entity to be sure to get the very last version of my entity(and its tranlsations). That is not perfect but it works for now.
IMHO we should only send one entity and a table of langcode to update.

What do you think?

Hmm. Well I'm inclined to commit #7, which worked as expected btw, even though it could be optimized better.

Since its going through a bulk update, and each selected "entity" is processed one by one, it makes sense to me to treat each translation as a separate entity even if that entity is a "shallow clone". The translations are also listed in the admin/content view as separate entities, so I'm personally ok loading and processing them as such, even if they arent really separate at all under the hood.

I'm also a bit concerned if we rewrite the process to deal with the shallow clones as a single entity, it might affect things like paragraphs, which I've found tricky to handle when they get nested a level or two.

I'll think it over, maybe test a bit more in a more complex scenario, and set for review. Maybe @supertony could try it out and see how it works for him in a real environment also.

Just a follow up about this feature, we've been using the patch for 7 months now and no bug have been reported so far by our clients