- 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
- First commit to issue fork.
- Status changed to RTBC
9 months ago 10:12am 12 August 2024 - πΊπΈUnited States pookmish
MR from #3 works as expected. There is minimal changes and nothing functionally different. Please release a Drupal 11 supported version.
- πΊπΈUnited States Chris Burge
chris burge β made their first commit to this issueβs fork.
-
chris burge β
committed 1bb6fa06 on 2.x
Issue #3433668 by chris burge, pookmish: Automated Drupal 11...
-
chris burge β
committed 1bb6fa06 on 2.x
- Status changed to Fixed
9 months ago 12:02am 17 August 2024 - πΊπΈUnited States Chris Burge
Access checks are only necessary on content entities, not on config entities: https://www.drupal.org/node/3201242 β .
- πΊπΈUnited States Chris Burge
Drupal 11 compatibility is released in 2.2.0 β .
Automatically closed - issue fixed for 2 weeks with no activity.