Closed (fixed)
Project:
ImageAPI Optimize WebP
Version:
2.1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Jun 2024 at 13:04 UTC
Updated:
5 Mar 2025 at 08:06 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
bharath-kondeti commentedIs this issue on Drupal 11 or Drupal 10 ?
This module does not have a release for Drupal 11 yet. It must be throwing from a patch from this issue https://www.drupal.org/project/imageapi_optimize_webp/issues/3448709
Comment #3
djdevinSorry this is actually Drupal 10.3!
But there is an issue in core to not break BC here: https://www.drupal.org/project/drupal/issues/3450244
However, from the issue:
So we may have to fix it here.
Comment #4
djdevinComment #5
djdevinSetting as needs work, since this is a BC break.
Comment #6
djdevinComment #7
michaellander commentedThanks for the patch. We'll likely need to create a 2.1 and make a requirement for 10.3 and above.
What I've found is the approach with this module and some of the others in the space are a bit dated(and require overriding a core controller which created this issue to begin with. I'm working on a potential new alternative that I think would be foundationally stronger, but in the meantime we'll keep supporting this.
Comment #8
taran2lComment #9
siramsay commentedI've applied the patch at #6 to a couple of site so far and can report it is working with 10.3.1.
Can we get a 2.1 version? Is there anyway I can help with that?
Comment #11
michaellander commentedComment #12
michaellander commentedHiding patch and moving to branch.
Comment #15
michaellander commentedComment #16
michaellander commentedComment #17
danielwirz commentedHi there
I also did a successful test of the patch. I also tested the 2.1-dev branch on my projects - also successful.
What is the timeline for the 2.1 release? Can I help you with this in any way?
Comment #18
michaellander commented@danielwirz, am wanting to include #3448709: Automated Drupal 11 compatibility fixes for imageapi_optimize_webp in a 2.1 release so we can confidently support Drupal 11. If you can help test the patch in that issue on 10.3 and 11, that'd be great.
Comment #19
michaellander commentedAlso going to test #3466630: Attempt to remove ImageStyleDownloadController override completely, which would really simplify things. In which case maybe we just move to 3.x if it works.
Comment #20
michaellander commentedIf we can get some more eyes on #3466630: Attempt to remove ImageStyleDownloadController override completely, I believe it'll make this update much easier overall. I think it allows us to keep this in 2.1, and should give us a path forward for modules like ImageAPI Optimize AVIF to run alongside this module without needing glue modules like ImageAPI Optimize AVIF & WebP
Comment #21
danielwirz commented@michaellander thanks for the feedback. i'll test the patch next week and give a feedback
Comment #23
v.dovhaliuk commentedSince using MR as a patch is a security issue, I'm adding a patch as a temporary solution until a new release of the module is added.
Comment #24
radio_babylon commentedso is this ever going into the module release version? i really need to be able to update some sites that break when i do... thanks!
Comment #25
radio_babylon commentedso i am guessing that is a 'no' and i need to remove the module then.
Comment #26
v.dovhaliuk commentedRerolled patch from #23 to add compatibility with Drupal 11.
Comment #27
chucksimply commentedSo is this already in the latest 2.1 released in Jan 2025? Patches aren't working.
Edit: Looks like no. Can we get some clarity as to the status of this MR? Do we need an updated patch for 2.1?
Edit 2: Patch #26 applies to 2.0.0 successfully. Fixes the issue and makes it compatible with D11
Comment #28
weseze commentedFor Drupal 10.3.x the latest version of this module (2.1.0) is working correctly.
The extra parameter ($required_derivative_scheme) was added in this release.
So not patch is needed for Drupal core 10.3x and 2.1.0 of this module.
As for Drupal11 compatibility: I do not know, have not tested this yet. But looking at the code it should work without the need for this patch.