- Issue created by @project update bot
- Open on Drupal.org →Core: 9.5.x + Environment: PHP 8.0 & MySQL 5.7last updateover 1 year 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.ymlfile 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 informationBot run #11-127659- These 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: 9.5.x + Environment: PHP 8.0 & MySQL 5.7last updateover 1 year ago Waiting for branch to pass
- Open on Drupal.org →Core: 9.5.x + Environment: PHP 8.0 & MySQL 5.7last updateover 1 year 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.3, cannot fix all Drupal 11 compatibility problems. - Therefore, these changes did not update the - info.ymlfile 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 informationBot run #11-199781- These packages were used to generate the fixes: - drupal/upgrade_status: 4.3.2
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.3
 
- Open on Drupal.org →Core: 9.5.x + Environment: PHP 8.0 & MySQL 5.7last updateover 1 year ago Waiting for branch to pass
- First commit to issue fork.
- Status changed to RTBC3 months ago 9:09pm 24 July 2025
- 🇸🇮Slovenia useernamee LjubljanaI checked MR9 with upgrade status and the scan did not return any known issues. Moving to RTBC. 
- 🇺🇸United States sprocketmanMR9 didn't work for me due to additional spaces before lines 78-80. 
- 🇺🇸United States euk@sprocketman In general... if you are using a patch form the MR there could be issues due to differences in the targets: MR9 is issued against the dev version, you might be trying to apply it against a release. I am attaching a patch that worked for me back when I created the MR9.