Hey @cbdgum, we would appreciate it if you can let us know what stopped working for you. I’m sure we can quickly fix this with an update. No need to do a 1-star rating, especially for something that worked perfectly but now just encountered a bug. Version 1.2.2 has been out for a month and we have not gotten reports similar to yours.
You can also download previous versions of Cimo from our plugin page, scroll down a bit and under Advanced Options you should see a dropdown with all the older versions available to download: https://ww.wp.xz.cn/plugins/cimo-image-optimizer/advanced/
A new plugin like ours have a few ratings, and a 1-star rating really hurts our visibility and standing. I do not believe a bug would warrant such a bad rating.
Some questions:
- What version did you upgrade from?
- What action did you perform that stopped working?
- Which page were you in when you uploaded the image?
- we upgraded on multiple sites from 1.2.1
- any upload no longer is optimized to webp as they did previously.
- this is from any page that has an option to upload media. from a blog post. from the media folder. from a product editing page. none of them are converting with 1.2.2 active. I will try to roll back to 1.2.1 and will report back as soon as I get that done.
I do plan to redo the review and fix the star rating. I am not one to leave dev’s hanging.
Turns out I had to roll back to 1.2.0 to gain functionality. Amended the rating, and looking forward to helping debug the issue myself and others seem to be having.
We must not have uploaded any images while we were on 1.2.1 to have noticed it not working on the sites.
Appreciate the amend @cbdgum, it means a lot!
Thanks for the information. I hope you can answer these:
- Are you uploading using Gutenberg? or are you using a page builder? If so, what version are you using?
- How are you uploading the images? For example, are you adding via a native image block?
In 1.2.1 we added this: “New: If the resulting optimized image is bigger than the original image, the image is now skipped and the original image is kept.” I’m thinking it’s possible this is what’s causing the issue.
Would you be able to check whether the optimized file you uploaded while using 1.2.0 resulted in a larger webp file? Starting 1.2.1, when this happens we halt the conversion if it resulted in a larger image and the original one is uploaded instead.
If you can confirm this is happening, you can decrease the quality for the conversion, right now we have it set by default to 80% quality. But you can decrease it to 70%.
We found an issue in v1.2.2 that may have caused this. Version 1.2.3 has just been release that fixes conversion for dropped images @cbdgum
Let me know if this fixes things!