That sounds like a plugin conflict, are you using any media library management plugins?
Thread Starter
j_sagu
(@j_sagu)
The plugins that I am using that are media related are
– Enable Media Replace
– Folders
– Media File Sizes
– WP Media folder
– WP Retina 2x
These are theme plugins
– Story Portfolio Items
– Story Recent Posts Widget
Thread Starter
j_sagu
(@j_sagu)
I am assuming WP Media folder could be the culprit? If so, I really need this plugin to keep everything organised.
At the moment, I am currently optimising already on WP 1 by 1, but if there’s a quicker way to do this, this would be great! 😀
You can switch to List view in the Media Library, and then increase the number of images per page to 100+ and use the select all + bulk actions drop down to do larger batches at once.
If I remember right, the last person who had this issue was using Enable Media Replace.
Thread Starter
j_sagu
(@j_sagu)
I tried this before but if I select more than one and do ‘bulk optimise’ it directs me to the EWWW optimise all page.. From there I get the same error as the initial error above.
Only time that it seems to work is when I do 1 by 1 but even then I have to re-optimise some images more than once for WebP to be shown..
Are you using lossy options? A WebP derivative may not be generated EVERY time, only when it is smaller. I wouldn’t recommend running an image more than once if you’re using lossy. You shouldn’t lose too much quality, but you lose a little bit more everytime you re-optimize an image that way.
Thread Starter
j_sagu
(@j_sagu)
No I have not checked ‘lossy’ compression…
Is there a way I can restore all the images to its original state so I can do the optimising again as I have done a few images a few times in order to get the WebP resizing to come up…
Thanks
As long as you’re using lossless mode then, you don’t have to worry about re-optimizing. You can do it a hundred times, and it won’t hurt anything.
Thread Starter
j_sagu
(@j_sagu)
Okay, should I not re-optomise in order to get the WebP appear?
Also not a quicker way to do it all at once apart from selecting all on a list mode as it keeps directing me back to the EWWW bulk optimising which doesn’t work which I am assuming is due to the folder management?
Thanks
Ok, let’s see if we can’t dig into the Bulk Optimize problem a bit here. You can re-optimize if you like, it shouldn’t hurt anything, because the webp should have the same contents in both cases (going to dig into that a little later to find out why the size is different though).
At any rate, can you start by disabling your other plugins, make sure the bulk optimize loads and runs properly (stop it after a couple images), and then re-enable the other plugins one by one until you find the one causing a conflict.
Ok, you were right, it IS WP Media Folder causing conflicts. I went back to my dev site and saw that was the plugin we had trouble with. I was never able to replicate the issue, but I could see what hooks in their code are messing with the Bulk Optimize code.
In digging through the get_posts() function and tracking things down the chain, I realized we are using a lot of complexity and overhead for a rather simple database query, so I swapped out get_posts for wpdb queries.
I have one or two more issues I’d like to fix for the next release, so the fix is currently in the dev branch here: https://downloads.wp.xz.cn/plugin/ewww-image-optimizer.zip
That should allow you to run a full Bulk Optimize on your images. It’s also a bit faster too, so that might clear up some of the weirdness with webp images not being generated.
Thread Starter
j_sagu
(@j_sagu)
Hey.
That’s awesome! Although I have managed to optimise all the images individually lol…
Where would I place this extracted zip folder within the WP site?
Thank you!
You would replace the existing ewww-image-optimizer folder with the contents of that .zip file. Or what I usually do is deactivate, delete the plugin, and then go to Plugins->Add New->Upload and do it that way.
Thread Starter
j_sagu
(@j_sagu)
Hey
If I do it either way, will the images that I have already optimised stay optimised?
Thanks
Yeah, the compression is permanent, and their status is tracked in the database, so the plugin won’t lose any memory of what is has done if it is temporarily removed.
