Hello @rodman38
We are going to look into the issue and get back to you shortly.
All the best,
WPvivid Support Team
Hello @rodman38
After checking the htaccess file and the video, our guess is that the issue can be related to web server or cache.
So here are 2 suggestions:
1. A Litespeed server requires a service restart for rewrite rules to take effect. So you can try to restart the Litespeed service to make CompressX rewrite rules effective. You can use the command below to restart the server service:
sudo service lsws restart
2. Another possible cause is CDN cache. If the site is using a CDN caching service, you can try to purge all cache and see if that resolves the issue.
All the best,
WPvivid Support Team
Hello @tonyrobins
I just restarted the LS Cache service via my host’s Cpanel but it still doesn’t work, I still have the .webp format which remains the priority, the .avif format is not active, however in the /wp-content/compressx-nextgen/uploads directory I have the images.
here is the example of the problem on a site => https://clemenceheller.pro
There is no CDN, what should we do now ?
Hello @rodman38
Thanks for the update.
It’s strange that we can see some AVIF images served on the website page.
Would you send us a Debug zip from the System Information page of the plugin so we could troubleshoot and suggest further?
All the best,
WPvivid Support Team
Hi @rodman38
Thanks for the update.
After troubleshooting the issue, we found that it’s a bug where in some cases AVIF cannot be displayed properly after converting WebP to AVIF, it’s actually caused by htaccess file.
We are preparing a new version which should be available in a day or two, we are going to let you know once it’s ready so you can update the plugin to get the fix.
Thanks for reporting and helping fix the issue.
All the best,
WPvivid Support Team
Hi @rodman38
Just a quick update:
As mentioned earlier, the new version 0.9.14 is available now.
Feel free to give it a try and let us know if the issue is resolved.
All the best,
Hi @tonyrobins
Thank you, for the moment, the update has not arrived (I am in France, that may be why)
@rodman38
You can also download it from this link – https://downloads.wordpress.org/plugin/compressx.0.9.14.zip
After updating the plugin on the site, you can deactivate then re-activate it to get the .htaccess file updated.
All the best,
Hi @tonyrobins,
I just updated the plugin, I disabled/enabled the plugin, but the problem persists, it still loads webp I purged the litespeed cache.
Here is a video capture =>https://www.awesomescreenshot.com/video/31252052?key=de6061df924adba63fb17bc554a0f610
What more needs to be done ?
it may be important to say it to debug, but before using your plugin, I used another similar plugin, this plugin deleted all my original images in jpeg/png format and converted to webp format, I didn’t like that Conclusion, it’s not your plugin that converted to webp formats, I had already.
Hello @rodman38
If it is Litespeed server, since a Litespeed server requires a service restart for rewrite rules to take effect, you can try to restart the Litespeed service to make CompressX rewrite rules effective. You can use the command below to restart the server service:
sudo service lsws restart
Let us know if that resolves the issue.
All the best,
@tonyrobins
I restarted the service, but it doesn’t work =>https://clemenceheller.pro
Hello, thanks for the update! We’ll take a look at your website and get back to you soon.
Hello @rodman38
We have conducted a comprehensive analysis of the issue. Based on the information you have provided, we can see two possible causes:
1. We found that the cache status of these problematic images is hit, see this screenshot, which means, they are cached. This suggests that the issue may still be related to cache.
2. According to your description:
but before using your plugin, I used another similar plugin, this plugin deleted all my original images in jpeg/png format and converted to webp format,
Since these images had already been converted, after being converted again by CompressX, the size of the converted image may be larger than the original image. While by default, CompressX will delete the converted version if it is larger than the original image (you can find this option in the plugin settings), it might be a cause too.
All the best,
