No, unchecking the box removes the future job from the queue, but pngout could be searched for during several different admin jobs, possibly even during the WP update checks.
The question that comes to mind immediately, is why do you have pngout enabled if it cannot be found?
Hi, we don’t have pngout enabled but still get these warnings. Sometimes less often, sometimes multiple times per day.
Our settings:
Scheduled optimization [ ]
Disable Automatic Optimization [ ]
disable jpegtran [x]
disable optipng [x]
disable pngout [x]
disable gifsicle [x]
Cron output:
sh: 1: pngout-static: not found
sh: 1: /usr/bin/pngout-static: not found
sh: 1: /usr/local/bin/pngout-static: not found
etc., 80 lines altogether about pngout-static
I’m suspecting this has to do with images automatically being saved by cron scripts. However, that shouldn’t trigger a search for pngout as it’s disabled, or should it? Is it normal that pngout is being looked for at irregular intervals, sometimes multiple times per day and despite it being disabled? If it is, is there a reason the result is being output into cron, and not handled silently or some other way?
For some reason we receive these emails from one site, and not the other, although the configuration is nearly identical in these regards. I’ve resaved the settings. I’ll let you know if that results in these emails stopping for a longer time.
That’s also a very old version of EWWW, and a bit strange that you have all the tools disabled unless you’re using the API, in which case you could just switch to this: https://wordpress.org/plugins/ewww-image-optimizer-cloud/
Well spotted on that version number. It’s actually 2.5.9, and the latest looks to be 2.9.3 now. For some reason WP hasn’t offered an update, and doesn’t, despite disabling and enabling plugin and then forcing a check again. Any idea what could cause this? Do later ones require a specific WP version?
We have the JPG compression enabled. We could re-enable the PNG ones, but there hasn’t really been a need for that recently. If the need becomes more pressing we’ll look into it and will keep the cloud option in mind, thanks. For now I’m just curious about whether there’s an unsolved bug I could help fix. Right now it looks like the first thing to figure out is the plugin version issue.
Yeah, the newer versions require WP 4.4+
