- 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 β these changes make this module compatible with Drupal 11! π
Therefore these changes update theinfo.yml
file for Drupal 11 compatibility.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 States brayn7 Lexington, Ky
I tested this on php8.3, D10.3, Looking in Upgrade Status it removes the warnings. I created templates and could place them.
- Status changed to RTBC
3 months ago 3:11pm 9 August 2024 - Status changed to Needs work
2 months ago 8:45pm 17 September 2024 - π―π΄Jordan Rajab Natshah Jordan
- Only replace the
watchdog_exception
- Change
1.1.x
branch to support Drupal<=10.2
- Start a new branch
1.2.x
to support Drupal^10.3 || ^11
- Only replace the
- First commit to issue fork.
- Merge request !29Issue #3434418: Automated Drupal 11 compatibility fixes for section_library β (Merged) created by Cyberwolf
-
rajab natshah β
committed 2da9bcf1 on 1.2.x authored by
cyberwolf β
Issue #3434418: Automated Drupal 11 compatibility fixes for...
-
rajab natshah β
committed 2da9bcf1 on 1.2.x authored by
cyberwolf β
- π―π΄Jordan Rajab Natshah Jordan
β Released section_library-1.2.0 β
Automatically closed - issue fixed for 2 weeks with no activity.