- Issue created by @project update bot
- last update
9 months ago 40 pass This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request 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.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug info
Bot run #11-121090This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
- last update
9 months ago 40 pass - last update
8 months ago 40 pass This comment was forced and has ignored the check if a change was already posted. This is only done when we want to update the issue without waiting for changes to happen.
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-137198These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.10
- palantirnet/drupal-rector: 0.20.1
- last update
8 months ago 40 pass - last update
6 months ago 40 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 → 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-188815These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.2
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.2
- last update
6 months ago 40 pass - 🇩🇪Germany Anybody Porta Westfalica
Now that Drupal 11 is out, any maintainer plans here?
- Status changed to Needs work
12 days ago 10:06am 22 November 2024 - 🇩🇪Germany Grevil
There are quite a few issues to solve first, before this is D11 ready:
- 🐛 Error: Call to a member function getConfig() OverridesSectionStorage.php Active
- 🐛 Calling ClassResolver::__construct without the $container argument is deprecated in drupal:10.3.0 Active
And other issues, that are not listed in the issues tab. I'll take a look, if we can simply fix the combined.
- Merge request !16Issue #3431600: Automated Drupal 11 compatibility fixes for layout_builder_st → (Open) created by Grevil
- 🇩🇪Germany Grevil
Ok, this seems to do the trick! If merged, we can also close the child issues!
Make sure to credit @justcaldwell and @almador, which helped me to fix / point out the issues!
- 🇩🇪Germany Grevil
Unsure about existing installations, since the dependencies changed. Some people (not using drush and or composer) might have problems with the update.
- 🇩🇪Germany Anybody Porta Westfalica
We're changing the services.yml - don't we need to clear the container cache @grevil?
- 🇩🇪Germany Grevil
We're changing the services.yml - don't we need to clear the container cache @grevil?
Last time I checked this, clearing the container cache did not make a difference, but yea, I can add that.