Problem/Motivation
A 2.0.x branch has been created, there's known test failures that will need some time to figure out.
Steps to reproduce
Run the pipeline and see the errors.
Proposed resolution
TBD
Remaining tasks
TBD
User interface changes
TBD
API changes
TBD
Data model changes
N/A
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | errors.patch | 1.51 KB | heddn |
| #2 | layout_builder_st-usage.png | 37.85 KB | joseph.olstad |
Issue fork layout_builder_st-3520741
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
joseph.olstadPossible lead to a fix.
Steps to reproduce:
Exception occurs
- edit the layout on the same node using french (the original/site default language), no error , able to edit the layout without exception.
see screenshot:

exception message follows: (from core)
Comment #3
joseph.olstadMy guess is, something in core changed between Drupal 9.5 through to Drupal 10.4 / Drupal 11.1 causing this exception to be thrown.
Actually, looks like some deprecation that was removed in PHP 8+ causing the exception. PHP 7.4 with Drupal 9.5 would not have crashed here.
Full stack trace of two possibly related errors.
Url:
/en/node/2277/layoutSecond error:
Url:
/en/node/2277/layoutComment #4
joseph.olstadComment #8
heddnThe easy fix was to pull in #3411037: Contextual links for translation are removed by core. However, I'm fully convinced that one of
are being faced. In
TranslateBlockForm::createTranslationElement, we interact with TypedData and that triggers validations of TypedConfigManager plugins in TypedDataManager. I'm not sure how to solve this. For now posting my findings.You too can reproduce this on a 10.4 or later site and this module.
drush en -y content_translation layout_builder_st field_uiComment #9
heddnIf you patch core with the attached test, something between 10.2.0 and 10.3.0 broke. This is the logic that lb_st is trying to do.
Comment #10
heddnThe trick seems to be adding
$definition->setTypedDataManager($this->typedConfigManager);in the form class. Manually testing and executing tests locally, things are now passing green again. Oh, I also had to fix some of the tests.However, #3127026: Not possible to override an entity type class multiple times is biting us from upstream so tests are again not passing green on the testbot.
Comment #11
joseph.olstadOk @heddn very good, you've fixed the Drupal 10.4.x testing somehow.However Drupal 11 testing results is curiously vastly different. Perhaps since it's testing against 11.x-dev instead of 11.1.8 or 11.2.2?If we're testing off of 11.x there is a higher chance of seeing turbulence when compared to say testing against 11.1.8 or 11.2.2.The Drupal 11 pipelines show 14 failures in the most recent run.Not sure if this is of any help however we have been successfully using layout_builder_st dev-2.0.x 68f690c8fb with Drupal 11.1.8 extensively with this concoction of patches:
This bunch of patches that have recently been merged.
#3411037: Contextual links for translation are removed by core
#3420063: Error: Call to a member function getConfig() OverridesSectionStorage.php
and
#3420063: Error: Call to a member function getConfig() OverridesSectionStorage.php
All of which have now been marked as fixed however they were NOT merged into 2.0.x for some reason
Others outside of my groups have builds with layout_builder_st dev-2.0.x with a variety of patches applied and using Drupal 11.1+
Wondering why Drupal 11..x-dev testing would suddenly show 14 pipeline failures. Previously there were 3 with 22 skips, maybe because now there's only 21 skipped? Maybe the non-skipped test has a lot of failures now that it's no longer skipped?
Prior to recent changes;
Tests: 38, Assertions: 1100, Errors: 1, Failures: 3, PHPUnit Deprecations: 1, Skipped: 22.https://git.drupalcode.org/project/layout_builder_st/-/jobs/5051465
Latest pipeline run:
Tests: 38, Assertions: 98, Errors: 14, PHPUnit Deprecations: 60, Skipped: 21.https://git.drupalcode.org/project/layout_builder_st/-/jobs/5051465
Comment #12
joseph.olstad@heddn, great work, seems like you've pushed things further along!OOPSSeems as if we forgot all the work that has been done in 2.0.x and that folks have been using 2.0.x with Drupal 11+
Comment #14
heddnThis goes a long way to improving tests. There are still failing tests, but they are blocked on #3127026: Not possible to override an entity type class multiple times landing upstream.
Comment #16
heddnComment #18
joseph.olstadSerious chaos has happened with layout_builder_st
we had @phenaproxima running things, he ended up doing a build of 2.0.x that we have been using successfully with Drupal 11.1.8
Now I see the latest 2.0.x won't even run testing as it says this:
@phenaproxima basically did some heavy modifications from 1x to 2.0.x. It was functional and we have been using it since several months. However there's now been a major reversal on the approach, a new maintainer, did you guys even have a discussion before handoff .
Here's what we have been using with Drupal 11.1.8
with these patches