Two things that help us know if it’s really a “problem” are these:
1. As you guessed, the trace log.
2. How many times has the image been re-optimized?
If #2 matches up with how many times you’ve adjusted/edited that logo, then don’t worry about it and just dismiss the notice.
But if it’s like 50x or something nuts, then there could be a bug.
Hi
2. The number of times is 6. I don’t believe I have edited the logo at all.
I have tried dismissing the message but it keeps coming back.
There are 7 sizes of this logo image, and they have all been re-optimized 6 times so far.
1. Trace logs for each size look exactly the same:
PHP trace:#0 ewww_image_optimizer() called at /var/www/vhosts/..../httpdocs/wp-content/plugins/ewww-image-optimizer/bulk.php:1915
#1 ewww_image_optimizer_bulk_loop() called at /var/www/vhosts/..../httpdocs/wp-includes/class-wp-hook.php:292
#2 apply_filters() called at /var/www/vhosts/..../httpdocs/wp-includes/class-wp-hook.php:316
#3 do_action() called at /var/www/vhosts/..../httpdocs/wp-includes/plugin.php:484
#4 do_action() called at /var/www/vhosts/..../httpdocs/wp-admin/admin-ajax.php:187
(I have replaced my site url with …)
That would appear to indicate that the image did change at some point (6 times or so), or the bulk optimizer got stuck on it once. In either case, it’s not enough to worry about, so I would just dismiss the notice and see if it comes back.
Thanks for confirming, but I have already tried dismissing the notice a few times, and it always comes back. We have the same issue on a number of our websites.
is there a way to clear the message so it doesn’t come back?
Ah, well that’s a different story. I don’t imagine you’re running the bulk optimizer constantly, but maybe someone setup a cron-job with WP-CLI?
Those are the only two cases where the ewww_image_optimizer_bulk_loop() function gets called.
In either case, it is strange that the image isn’t tracking properly in the db though. Such behavior usually indicates the file size of the image is repeatedly changing, since that’s the only way to “trick” EWWW IO into re-optimizing an image (without the force re-optimize option). If the file size doesn’t change from what EWWW IO has saved in the wp_ewwwio_images table, it knows the image has already been optimized and skips it.
Could be a bug in your theme triggering a re-crop, but since we don’t have a direct trace from where the image was (re)created, it’s hard to pin down exactly how this is happening.
I *would* like to verify that there isn’t some quirk in EWWW IO triggering a false positive though, but for that we’d need debug logs, so if you want to tackle that, please use https://ewww.io/contact-us/ and reference this thread. I’ll follow up with you from there.
Otherwise, you can try to have a developer dig into the potential “bug” more–verifying whether the file size of the image in question is changing regularly, checking what size is tracked in the wp_ewwwio_images table for that image, and then seeing if they can pin down the offending code.
Or you can just put that image into the Files to Ignore setting on the Advanced tab and not worry about it.
To clarify, I am only using the free plugin, so I do not have the IO setting ticked.
I think I ran the force optimise yesterday after ticking the WebP option. and it does say that the last time it re-optimized was 1 day ago which would make sense. I got the alert afterwards and clicked the reset counters button yesterday, but it came back again today. As I say, I have seen this alert pop up on other sites of ours (built in same way), although I can’t find one as an example at the moment – typically.
I am using Astra pro theme, everything is up to date.
I have submitted my debug information to the contact form popup on your website as instructed.
Thank you.
