Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.No need to really commit this unless the other issue makes it in, but because it turns out to break a bunch of stuff I'm guessing that's never happening.
This is the issue in question that makes sure inline blocks export their UUID, so people can actually migrate layouts, etc without having to do postProcessing from hell.
#3180702: Export block UUID with custom Layout Builder blocks
But because loading by UUID takes precedence over revision_id, and this module's widget only updates the revision_id that other issue breaks the whole copy blocks during translation flow.
A quick patch fixes it though.
| Comment | File | Size | Author |
|---|---|---|---|
| layout_builder_at.support_block_uuid.patch | 657 bytes | grayle |
Issue fork layout_builder_at-3211413
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:
changes
Comments
Comment #2
swentel commentedOk, I followed the issue, so I'll know when it get's in. We'll have to tag a release targetting 9.2 - or maybe some other funky check, maybe using the Drupal Constant :)
Comment #3
WebbehComment #4
svendecabooterComment #7
svendecabooterThanks for the patch.
It doesn't look like UUID export will be committed to core anytime soon, but in the meantime we can already add support for people using this patches in the referenced issue.