I'm not sure if this is a bug, or I'm missing a step somewhere. Equally, I'm not sure if this is the right place, or if I should have put this under imageapi_optimize.

I have both modules enabled, using either the default pipeline with all processors or my own pipeline using with just the processors I have binaries for, and my images are still the same size.

I have set a sitewide default processor.

I've cleared caches, run cron, flushed the image cache, but still nothing.

I'm not seeing anything in the logs either.

I see the last comment on this post talks of a similar issue: https://www.previousnext.com.au/blog/better-image-optimisation-drupal

Am I missing something, or is this a bug?

Thanks for any help!

CommentFileSizeAuthor
Screen Shot 2019-06-13 at 16.44.55.png75.84 KBashleyhazle
Screen Shot 2019-06-13 at 16.45.02.png52.9 KBashleyhazle

Comments

ashleyhazle created an issue. See original summary.

ashleyhazle’s picture

ashleyhazle commented
Issue summary: View changes
Hyperfocused’s picture

Hyperfocused commented

I'm in the same situation as you, and also read the last comment of that blog post. I guess it's a bug that needs fixing. Also see this outstanding issue thread: https://www.drupal.org/project/imageapi_optimize_binaries/issues/2452111

steven jones’s picture

steven jones commented
Status: Active » Closed (cannot reproduce)

Honestly, I think this is because in an number of our processors we were hard-coding the quality settings so high the images weren't being recompressed enough. We are resolving those issues now and we are reducing the size of images, promise!

If you wanted to, please make a follow up ticket about adding some logging/stats for pipelines so you can at least have a look in the watchdog for compression goings on.