Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.If you enable the layout on the manage display BEFORE you enable this module, the field isn't marked as translatable.
We should add something that makes these fields translatable. The field is locked, so we should probably just add our own config section somewhere where we can list the fields and add an operation to make them translatable.
Another idea was to make all those fields translatable on install, which would make sense initially. However, allowing to toggle it is interesting too, because on some entity types / bundles, you might not want to have the asymmetric translation.
Issue fork layout_builder_at-3054967
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
swentel commentedComment #3
portulacaI had the custom layout created on Article before enabling this module and as expected can't get the translation to work.
I now enabled the Layout Builder on Basic Page (after the LBAT has been installed), but only one of the fields is showing on View, something seems to be very wrong. And I don't have any Pages with overriden layout but I can't turn LB off for Pages (checkboxes are disabled stating customized layouts need to be reverted to be able to turn them off).
Is this related to LB Asymmetric Translation or do I also need to revert the Article custom layouts so I can turn off LB on Page content type?
Comment #4
swentel commentedHmm, dont' think so, but I'm not 100% sure to be fair. I haven't tested with another content type yet, so I'll see what happens if I do that too.
Comment #6
swentel commentedExisting fields are made translatable on install.
Comment #7
swentel commented