- 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
- Status changed to Needs review
about 1 year ago 11:10pm 24 March 2024 - First commit to issue fork.
- heddn Nicaragua
The deprecated field type and render element will not be upgraded to support Drupal 11. If a site is using those, they should convert to using the supported field type.
-
heddn →
committed 12f5f360 on 8.x-1.x authored by
project update bot →
Issue #3434300 by heddn, project update bot: Automated Drupal 11...
-
heddn →
committed 12f5f360 on 8.x-1.x authored by
project update bot →
Automatically closed - issue fixed for 2 weeks with no activity.