The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Problem/Motivation
Currently, GD library will put a warning on the Status report if an image file format, such as AVIF, is not supported by the PHP installed on the system. I don't think this should be a warning. There is no need to support AVIF if the site has no need for it.
This check was added in commit 00d6bd9 for #3116611: Add a requirements check for GD support of allowed image types.
Proposed resolution
Use a different RequirementSeverity value so that the message appears with other status messages.
Remaining tasks
Screenshot report before and after
User interface changes
The GD library message appears with other status messages instead of as a warning.
Introduced terminology
None.
API changes
None.
Data model changes
None.
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | Screenshot 2026-04-09 at 2.43.24 PM.png | 335.87 KB | sivaji_ganesh_jojodae |
Issue fork drupal-3570466
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3570466-reduce-severity-of
changes, plain diff MR !15149
Comments
Comment #3
liam morlandThis merge request makes the GD library message a regular status message.
Comment #4
nicxvan commentedI think this is a good idea! Just a couple of questions.
Do you have before and after screenshots?
Also shouldn't it be RequirementSeverity::Info?
Finally, while I agree with you, do we need @heddn to comment as the image maintainer?
Maybe we can ask in slack. I'm not tagging for subsystem maintainer review because I'm not sure.
Comment #5
sivaji_ganesh_jojodae commentedSee the before and after screenshot added below.
Comment #6
liam morland@sivaji_ganesh_jojodae thanks for the screenshots.
I didn't set
RequirementSeverity::Infobecause I made it match the other code already there. If it is supposed to have that, I'm not oppose to adding it.Comment #7
smustgrave commentedCan we update the summary to show the git history where this was added and see if there was discussion around it. Probably needs submaintainer sign off before removing.
Comment #8
liam morlandComment #9
mstrelan commentedIdeally we could check if there are any image styles using the unsupported format to determine the severity, but that might be a bit too much overhead. Otherwise I guess this makes sense, especially since the existing message makes it sound optional, "if you want to add support".
Comment #10
jrochate commentedWorks great on Drupal 11.4.1 and it's a logical fix. This warning doesn't deserve so much attention unless image style audit referred by @mstrelan exists and is positive. Thank you.
Comment #11
liam morlandComment #12
liam morlandScreenshot is available in comment #5. Thanks
Comment #13
smustgrave commentedPer sign off in #9
Comment #16
catchMakes sense to me too, it's something that can be improved rather than a real problem.
Committed/pushed to main and cherry-picked to 11.x, thanks!