Problem/Motivation

This issue seems to have been reported a couple times (and fixed) over the past couple years. But doesn't seem to be fixed.

I am trying to use the Layout Library module and it works as expected until i try to add a block to a layout. Then i get this error:
TypeError: Argument 1 passed to Drupal\core_context\EventSubscriber\SectionComponentRenderArray::getContextsFromSectionStorage() must implement interface Drupal\layout_builder\SectionStorageInterface, null given, called in E:\www\drupal9\web\modules\contrib\core_context\src\EventSubscriber\SectionComponentRenderArray.php on line 89 in Drupal\core_context\EventSubscriber\SectionComponentRenderArray->getContextsFromSectionStorage() (line 112 of E:\www\drupal9\web\modules\contrib\core_context\src\EventSubscriber\SectionComponentRenderArray.php)

This is core 9.2.11 with latest versions of Core Context and Layout Library. Disabling CC and LL works fine.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
#5 3263703-05.patch828 bytesjoseph.olstad
#3 3263703.patch924 bytesjoseph.olstad
Command icon 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

liquidcms created an issue. See original summary.

liquidcms’s picture

Issue summary: View changes
joseph.olstad’s picture

StatusFileSize
new924 bytes

Patch to the rescue

joseph.olstad’s picture

Status: Active » Needs review
joseph.olstad’s picture

StatusFileSize
new828 bytes

here's a simplified/improved version of the patch.

joseph.olstad’s picture

tripodcreative’s picture

Guys, we need a patch for this to be committed to latest code so that it remains compatible with subsequent versions of Drupal. Page manager and layout builder are essential functions to modern Drupal sites - we're cloning sites from D7 to D9+ and asking clients to pay for this clone and to stick with Drupal as a CMS. I can't expect standard users to have to apply patches within composer.json and use in a production environment hereafter. When can we expect a stable release of this fix?

japerry’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

phenaproxima made their first commit to this issue’s fork.