Automated Drupal 11 compatibility fixes for vlsuite

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.9
3. palantirnet/drupal-rector: 0.20.1

Core 11 compatibility key points:
1. Dependencies version upgrade:

    "drupal/entity": "^1.4",
    "drupal/layout_builder_at": "^2.13",
    "drupal/layout_builder_operation_link": "^2.1",
    "drupal/layout_builder_restrictions": "^2.17",
    "drupal/media_library_form_element": "^2.0",
    "drupal/media_responsive_thumbnail": "^1.5",
    "drupal/section_library": "^1.1"

2. Patches:

"drupal/core": {
        "3207875 - \"Unsaved changes\" message incorrectly appears on layout builder": "https://www.drupal.org/files/issues/2021-08-13/3207875--20.patch",
        "3030154 - layout_builder__layout_section column hitting database limit": "https://www.drupal.org/files/issues/2023-04-06/3030154-62_0.patch",
        "3045509 - EntityFieldManager::getFieldMap() doesn't show bundle fields": "https://git.drupalcode.org/issue/drupal-3045509/-/commit/2d55b4ff75f2f7358ff765f3ec63591e45ca6f15.patch"
      },
      "drupal/section_library": {
        "3217647: Adding stuff to library doesn't close dialog if dialog opens in popup": "https://www.drupal.org/files/issues/2021-06-07/section_library.3217647.close-dialog.2.patch"
      }

3. Main VLSuite module & all others inside

Created 2.x branch in origin that will be compatible with core 11 & it will drop compatibility with already end of life core 9 (changed MR to point that branch)
Related:
Drupal 9 is end of life - PSA-2023-11-01: https://www.drupal.org/psa-2023-11-01 →
Drupal.org release version numbers allow semantic versioning: https://www.drupal.org/node/3108648 →

Added modules dependencies directly as related issues for core 11 compatibility.

Also related:
https://endoflife.date/drupal
https://www.drupal.org/about/core/policies/core-release-cycles/schedule →

Manually checked 2.x-dev into existing installation, basis review with no regressions detected (core 10, 11 still unable to resolve composer dependencies, see related issues, "composer require 'drupal/vlsuite:2.x-dev@dev' 'drupal/media_library_form_element:2.0.6 as 2.1.0' -W").

Waiting some advance into related modules compatibility and/or core release schedule.

To use with core 11 using composer:
Make sure vcs of compatible core 11 module dependencies are defined before "https://packages.drupal.org/8"

  "repositories": [
        {
            "type": "vcs",
            "url": "https://git.drupalcode.org/issue/layout_builder_at-3431569.git"
        },
        {
            "type": "vcs",
            "url": "https://git.drupalcode.org/issue/media_responsive_thumbnail-3431911.git"
        },
        {
            "type": "composer",
            "url": "https://packages.drupal.org/8"
        }
    ],

Then:

composer require "drupal/layout_builder_at:dev-project-update-bot-only#1711072acdd1316d2648372557bf4273a9352e66 as 2.x-dev"
composer require "drupal/media_responsive_thumbnail:dev-3431911-automated-drupal-11#37e476ed5555d8b4d63c273a581da67ebd2ee445 as 1.x-dev"

composer require 'drupal/vlsuite:^2.0'

Fixed config UI 2.x for core 11 with compatibility with ^10.3, also indcluded minimal test coverage (all config pages responds with response code 200).

Removed composer dependencies (& moved as suggestions) of:
- layout_builder_at
- media_responsive_thumbnail

Those dependencies are now managed by those using new vlsuite_demo preset (old vlsuite_shuttle now with just basis for a customized installation):
https://www.drupal.org/project/vlsuite/issues/3479416 ✨ Customized installation refinement Active

That will be included into release notes when new stable version comes.

NOTE: That just will affect to new 2.x version, 1.x keeps as it is. That way those modules won't affect for new installations in core 11 & no complete demo preset is needed.

Fixed "AssertionError: "..." must be defined in MODULE_NAME.field_type_categories.yml in assert()" when creating new field for core 11 into 2.x

crzdev → closed merge request !41

All adjustments ready, it should be working with core 11, for existing sites installed by shuttle: https://www.drupal.org/project/vlsuite/issues/3435575#comment-15800647 📌 Automated Drupal 11 compatibility fixes for vlsuite Needs work

Closing this issue, 2.x release out today

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