- 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 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, 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-120835This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
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-188138These 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
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
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-199781These 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
- Status changed to Needs work
3 months ago 3:11am 7 November 2024 - 🇦🇺Australia mstrelan
I tested this on 11.0.x and had a few issues.
\Drupal\image\Controller\ImageStyleDownloadController::deliver
now expects 4 params but we're only passing 3, for testing I hardcoded'public'
as the fourth paramimage/avif
was not listed in$request->getAcceptableContentTypes()
, I'm not sure yet why not, but I commented out this check to test if everything else was working- I had issues getting the conversion to work with ImageMagick. Not sure why, but after switching to the GD patches I was able to get this to work
- First commit to issue fork.
- 🇦🇺Australia mstrelan
Tested this with Drupal 11, with ✨ Let GDToolkit support AVIF image format Needs work and ✨ Add support for GD Needs review and can confirm it's working as expected.
I think we need to add a version constraint to composer.json since we have breaking changes for Drupal < 10.3 so sites on 10.2 can't accidentally update to this. Or does the composer facade handle this automatically from the .info file?
- 🇦🇺Australia nterbogt
I've merged to 1.1.x for now... have to make a few other changes before I can roll a release. So will confirm if composer restrictions are working as expected.
-
nterbogt →
committed fce3a092 on 1.1.x authored by
project update bot →
Issue #3428929 by project update bot, acbramley, mstrelan: Automated...
-
nterbogt →
committed fce3a092 on 1.1.x authored by
project update bot →
- 🇦🇺Australia acbramley
Thanks @nterbogt! Let us know if you need a hand with any of the other changes :)