- Issue created by @svendecabooter
- 🇧🇪Belgium svendecabooter Gent
MR added for this functionality.
Also attaching as a patch file, for Composer based patching workflows.
Currently there is logic in LbAsymmetricExtractor that, for each cloned Layout Builder block, loops over the translated data, and sets the values for all fields on the cloned block, via the default Field API ->set() method.
However, a more robust solution would be to use the appropriate FieldTextExtractor plugin for each of the fields to set their value, given their original data was extracted using this plugin, so it would make sense to have the value also being set by the same plugin. This allows each plugin to take care of their own special cases.
This would for example add support for the custom_field module, where a Layout Builder block could contain a custom_field field. The FieldTextExtractor plugin for custom_field (being worked on in 📌 Add support for AI submodule "ai_translate" FieldTextExtractor plugin Active would then take care of setting the current values.
Active
1.0
Code
MR added for this functionality.
Also attaching as a patch file, for Composer based patching workflows.