- Issue created by @nod_
- π¬π§United Kingdom catch
Adding some related issues from the XB issue queue.
- First commit to issue fork.
- Merge request !11972Remove Layout Builder dependency for the config and rendering of the Navigation sidebar β (Open) created by casey
- π³π±Netherlands casey
I've created a MR that removes the dependency on layout_builder while keeping the same config format for navigation.block_layout. The dependency is removed by simply calling the Layout and Block plugin managers directly.
The UI is still to be replaced. I only emptied navigation LayoutForm and added a new route "navigation.layout" to replace "layout_builder.navigation.view".
- Status changed to Needs review
11 days ago 9:29am 5 August 2025 - ππΊHungary GΓ‘bor Hojtsy Hungary
This currently moves down the dependency to layout_discovery. Is that a module that stays around in core? (There are a lot more criteria of course, but it is also not depended on by Experience Builder or UI Suite that I could find at least).
The Needs Review Queue Bot β tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide β to find step-by-step guides for working with issues.
- π¬π§United Kingdom catch
@gΓ‘bor hojtsy layout_discovery provides the layout plugin manager service definition.
π Add support for layout plugins Active doesn't depend on the layout_discovery service but it does depend on the same layout plugin manager class that the service uses (which is in Drupal\Core).
So I think that even if we eventually deprecate the layout_discovery module, the layout plugin manager itself will need to exist for quite a long time to support the just in time layout builder -> xb upgrade path. That could mean that navigation module ends up adding it's own version of the layout plugin manager or something like that - but it should be a relatively small incremental step to remove that dependency if/when we get to that point.