- Issue created by @jeroen dost
- 🇳🇱Netherlands jeroen dost
LS,
I guess, the answer will be "won't fix", because it has to be light weighted compared to Paragraphs. So we probably need to work around that. Has anyone tried to solve this problem? Copying the field from the source language when the source changes? Or a button adding this feature? Or other options?
Thanks in advance!
- 🇬🇷Greece vensires
It indeed seems as a "won't fix" but we might have a workaround which could even play fine in every website I think.
We could use the field type'spreSave()
function and make sure that even though the whole field is translatable according to Drupal settings, for each translation we get the value from the source and copy it over to the other translations. It is indeed a duplication of the value but might work.Of course, translatable fields get displayed in every language so I don't think we could hide it somehow like normally done for non-translatable fields. Field properties are not the same as Fields, so we don't have the same functionalities. It's an approach that might work though if anyone is interested.