- First commit to issue fork.
- last update
10 months ago 40 pass - 🇧🇪Belgium dieterholvoet Brussels
Rebase was a bit too complex so I merged 8.x-1.x in the issue fork.
- last update
10 months ago 40 pass - 🇧🇪Belgium dieterholvoet Brussels
The latest state of the MR doesn't fix the issue for me. When saving a translation, I get 'Non-translatable field elements can only be changed when updating the current revision.'. This issue is not present when I apply the patch from #41.
In both cases I do have another issue: I still get the 'Invalid translation language (und) specified' error, unless I add the following snippet, in that case everything works as it should.
- $target_entity->addTranslation($active_langcode, $target_entity->toArray()); + $target_entity_translation = $target_entity->addTranslation($active_langcode, $target_entity->toArray()); + if (\Drupal::hasService('content_translation.manager')) { + $manager = \Drupal::service('content_translation.manager'); + $manager->getTranslationMetadata($target_entity_translation)->setSource($target_entity->language()->getId()); + }
I have seen this fix/workaround be necessary for multiple other modules dealing with translations, so I'll add it here as well.
- #2593509: Set source language in content entity source →
- 🐛 "Invalid translation language (und) specified" when creating/updating translations Needs review
- 🐛 Node menu link translation breaks content translation Needs review
- #3118218: "Invalid translation language (und) specified" when generating translated content →
It's probably an issue with content_translation, but I haven't been able to figure that out.
- Status changed to Needs work
4 months ago 9:16pm 2 August 2024 - First commit to issue fork.