Automated Drupal 11 compatibility fixes for layout_builder_at

This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request is also openend and updated.

It is important that any automated tests available are run and that you manually test the changes.

Drupal 11 Compatibility

According to the Upgrade Status module → , even with these changes, this module is not yet compatible with Drupal 11.

Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.

Therefore these changes did not update the info.yml file for Drupal 11 compatibility.

Leaving this issue open, even after committing the current patch, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.

Debug info

This patch was created using these packages:

1. drupal/upgrade_status: 4.1.0
2. mglaman/phpstan-drupal: 1.2.7
3. palantirnet/drupal-rector: 0.20.1

This comment was forced and has ignored the check if a change was already posted. This is only done when we want to update the issue without waiting for changes to happen.

This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.

It is important that any automated tests available are run and that you manually test the changes.

Drupal 11 Compatibility

According to the Upgrade Status module → , even with these changes, this module is not yet compatible with Drupal 11.

Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.

Therefore, these changes did not update the info.yml file for Drupal 11 compatibility.

The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.

Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.

Debug information

These packages were used to generate the fixes:

1. drupal/upgrade_status: 4.1.0
2. mglaman/phpstan-drupal: 1.2.10
3. palantirnet/drupal-rector: 0.20.1

This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.

It is important that any automated tests available are run and that you manually test the changes.

Drupal 11 Compatibility

According to the Upgrade Status module → these changes make this module compatible with Drupal 11! 🎉
Therefore these changes update the info.yml file for Drupal 11 compatibility.

Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.

Debug information

These packages were used to generate the fixes:

1. drupal/upgrade_status: 4.3.2
2. mglaman/phpstan-drupal: 1.2.11
3. palantirnet/drupal-rector: 0.20.2

Any progress with core 11 compatibility?
Stable 11.0.0 is out since 2 August 2024 & current version is 11.0.5 (3 October 2024), maybe at least adjust "core_version_requirement" with "|| ^11" as first step to allow composer install, any other adjustment cannot be checked without possibility to install it. Thanks in advance!

If anyone needs to add this module to a D11 project, here are instructions if you have not done it before.

Add the patch in your composer.json patches section.

            "drupal/layout_builder_at": {
                "#3431569": "https://git.drupalcode.org/project/layout_builder_at/-/merge_requests/14.diff"
            }

If you don't have composer-drupal-lenient yet, add it to your project first:
composer require mglaman/composer-drupal-lenient

If your minimum stability is not set to dev yet, you need to do that first:
composer config minimum-stability dev

Add this module to the lenient allowed list:
composer config --merge --json extra.drupal-lenient.allowed-list '["drupal/layout_builder_at"]'

Now you can add this module to your D11 project:
composer require drupal/layout_builder_at

And of course you can enable it
drush en layout_builder_at

For 2.13 version use this patch.

Reviewed the MR and this seems to work as intended for Drupal 11.
Can this be merged in and a new release created with Drupal 11 support, given Drupal 11 has been released for a while now?

It breaks in Drupal 11.1 because it does not have the function layout_builder_at_form_entity_form_display_edit_form_alter anymore, which is used by this module.

Please check this patch that adds backwards compatibility among different Drupal versions. if you see it ok, we can add it to the bot merge request.

Tested and works great, would be nice to get this in an official release. Thanks!

Hoping for a tag release soon to ease and speed up testing and updates in projects.

📌 Offering to Support and Maintain the Layout Builder Asymmetric Translation module Active

FYI: I'm also applying to become co-maintainer of this module, to be able to push a D11 release: https://www.drupal.org/project/projectownership/issues/3497924 📌 Offering to co-maintain layout_builder_at Active

Nice, Sven!

I'd be happy if you maintain the module. It's a time commitment, and any effort to save that for others is truly appreciated.

I noticed the comment in 📌 Automated Drupal 11 compatibility fixes for layout_builder_at Needs review
https://www.drupal.org/project/projectownership/issues/3497924#comment-1... 📌 Offering to co-maintain layout_builder_at Active

We have many projects to upgrade to Drupal 11 and are hoping for a release for this project soon!

Created a new 3.0.x branch for D11 support, and to support semantic versioning.

D11 compatibility now available in 3.0.x branch. I will create a new release as well.

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