Automated Drupal 11 compatibility fixes for seven

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

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.2, 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.3.2
2. mglaman/phpstan-drupal: 1.2.11
3. palantirnet/drupal-rector: 0.20.2

vishalkhode → made their first commit to this issue’s fork.

Attaching patch from MR-8

Tested on:
- Drupal 11.0.1
- PHP 8.3.10
- MySQL 8.0.19

Verified:
- Seven can be installed in "Appearance"
- Seven can be used as the Administration theme
- Seven settings can be view and saved (/admin/appearance/settings/seven)
- Layout is the same as the Drupal 10 version
- Image widget appears as expected

Automated test ran with success
- tests/src/Functional/SevenLayoutBuilderTest.php
- OK (1 test, 13 assertions)

Please commit

+

Please accept the merge request, or the patch 📌 Automated Drupal 11 compatibility fixes for seven Needs review .

This is blocking a lot of Drupal sites from updating to Drupal 11, since even if you apply the patch using composer patches, the update to Drupal 11 is not working.
Tbh I have not found the reason yet why this is happening. For some reason within the composer.lock file is showing the following lines.

        {
            "name": "drupal/seven",
            "version": "1.0.0",
            "source": {
                "type": "git",
                "url": "https://git.drupalcode.org/project/seven.git",
                "reference": "1.0.0"
            },
            "dist": {
                "type": "zip",
                "url": "https://ftp.drupal.org/files/projects/seven-1.0.0.zip",
                "reference": "1.0.0",
                "shasum": "88e86926388c7e6cf66b0502d13a0470ce2399cd"
            },
            "require": {
<strong>"drupal/core": "^9 || ^10"</strong>
            },

Which is causing the update to D11 to fail.
So my assumption was that there is a composer.json within the contrib theme which is revering to D9 and D10 which also needs to be adjusted. But ... there is no composer.json and so I am wondering why I got that reference to drupal/core 9 and 10 within my composer.lock file.

@sgurit and other than use composer, The following can be added to composer.json. The simplest addition is

    repositories: [
        {
            "type": "vcs",
            "url": "https://git.drupalcode.org/issue/seven-3434485.git"
        },
    ]
  require: {
        "drupal/seven": "dev-3434485-d11-compatibility",
  }

If you are using admininal_theme then more information is needed and admininal_theme brings in seven automatically. The fuller version for seven is need as the theme specifies a version number and the version number is added by the Drupal's composer endpoint interface. The Reference value is the full commit hash for the latest commit.

repositories: [
        {
            "type": "package",
            "package": {
                "name": "drupal/seven",
                "version": "1.99",
                "type": "drupal-theme",
                "source": {
                    "url": "https://git.drupalcode.org/issue/seven-3434485.git",
                    "type": "git",
                    "reference": "0c070973e2d97d4a19f04cf99408e22bc9856fef"
                }
            }
        },
        {
            "type": "vcs",
            "url": "https://git.drupalcode.org/issue/adminimal_theme-3460890.git"
        },
    require: {
        "drupal/adminimal_theme": "dev-3460890-drupal-11-compatability",
    }