Incompatible with Layout Builder UX module

Created on 1 November 2020, almost 4 years ago
Updated 30 January 2023, over 1 year ago

Clicking to add a new section and then choosing the layout from the list results in the following error.

Drupal Core 8.9.7
Barrio 5.1.4 (also tried Bartik same issue)
Display Suite 8.x-3.9
Layout Builder Restrictions 8.x-2.7
Layout Styles 8.x-1.0-beta2 (disabling fixes the issue)

Enabled layout in display on a specific content type. Using the layout tab to go in and add a new section using layout builder slides out the right information panel displaying different layouts. Upon choosing one the following error is generated in the background:

Error: Call to undefined method Drupal\layout_builder\Form\ConfigureSectionForm::getLayout() in layout_builder_styles_form_layout_builder_configure_section_alter() (line 95 of /var/www/html/web/modules/contrib/layout_builder_styles/layout_builder_styles.module)

I have also tried restricting layouts to just those in the Bario theme in case there was something there but no joy.

Feature request
Status

Needs review

Version

1.0

Component

Code

Created by

🇦🇺Australia Greenman77

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇮🇳India MeenakshiG New Delhi

    I was stuck in the same issue but with a recent version of the module.
    Re-rolled patch as per the recent changes.
    Thanks

  • Status changed to Needs review over 1 year ago
  • 🇳🇴Norway TwiiK

    Upgraded core and all modules to the latest versions on the site I'm working on, and the patch in #9 stopped working. Not having the patch still causes the same error as described in the issue description when trying to select section layout. The patch in #10 was a drop-in replacement for the old patch, and fixes the error just like the previous patch did.

    I'm not using the https://www.drupal.org/project/lb_ux module though so the issue title is not what applies to me at least. I do think I may have evaluated lb_ux at one point, so maybe I ended up taking some of the functionality from it and putting it in a custom module instead. So it may very well be that I'm still doing something similar as that module did.

Production build 0.71.5 2024