- Issue created by @project update bot
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
Bot run #11-127659These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.9
- palantirnet/drupal-rector: 0.20.1
- 🇬🇧United Kingdom longmtran
Hi, any chance we can merge this change in soon? The patch works for me.
- 🇬🇧United Kingdom longmtran
Bumping this up. Patch is straightforward, just need this + another patch for the info file and it works as normal. Could the maintainer have a review please? Thanks
- First commit to issue fork.
- 🇧🇬Bulgaria nikolabintev
The patch is updated, so the logger factory service is used for error logging and the D11 version is added to the info.yml file.
- 🇪🇪Estonia tormi Tallinn
Here's Drupal 11 patch with a bit more D11 compliance updates against v2.0.10.
- 🇪🇪Estonia tormi Tallinn
New version which should apply without source install method.