- Issue created by @project update bot
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.0 & MySQL 5.7last update
8 months ago Waiting for branch to pass 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
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.0 & MySQL 5.7last update
8 months ago Waiting for branch to pass - First commit to issue fork.
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.0 & MySQL 5.7last update
8 months ago Waiting for branch to pass -
Rajeshreeputra →
committed 586d8dfb on 2.x authored by
Project Update Bot →
Issue #3433885 by Project Update Bot, Rajeshreeputra: Automated Drupal...
-
Rajeshreeputra →
committed 586d8dfb on 2.x authored by
Project Update Bot →