Ben Andersen

Thank you for the fix @shortpixel! I’ve tested it and it works!

@smithnguyen give it a try.

@smithnguyen ShortPixel has a possible solution to the issue introduced after the Litespeed cache plugin update. They’ve implemented it on my dev site and it works. Webp images are created and does not get deleted after creation! ??

@qtwrk Something changed from Litespeed cache 5.3.3 to 5.4 making webp generation not working. @shortpixel Can tell you more about this.

@berniesamui Try this in Custom CSS in the settings for GTranslate.

.glink { padding: 0px 4px; }

@serpentdriver I’m trying to get ShortPixel to answer here. I hope they will. I can’t really understand why the webp generation with ShortPixel worked for years with pure coincidence and now stopped working all the time. And ShortPixel can’t reproduce the issue it with LiteSpeed they say.

Would a plugin like EWWW work with LiteSpeed?

@serpentdriver Exactly! That is the problem.
When I upload them to the media library ShortPixel should create them (once). But it does not happen when LiteSpeed cache plugin is active. This has worked until 1 month ago. Why has it stopped? Did something change in LiteSpeed or ShortPixel?
I think you understand my problem now?

@serpentdriver Thanks, this is what the webp part looks like in the .htaccess file:

### marker WEBP start ###
RewriteCond %{HTTP_ACCEPT} "image/webp"
RewriteRule .* - [E=Cache-Control:vary=%{ENV:LSCACHE_VARY_VALUE}+webp]
RewriteCond %{HTTP_USER_AGENT} iPhone.*Version/(\d{2}).*Safari
RewriteCond %1 >13
RewriteRule .* - [E=Cache-Control:vary=%{ENV:LSCACHE_VARY_VALUE}+webp]
### marker WEBP end ###

Example of working url with webp:
https://lotuseco.se/shop/klanning-dam-oversize-crepe-naturvit/

Example of non working url where webp has not been generated:
https://lotuseco.se/shop/klanning-oversize-fickor-finrandig-bla/

Please look in the .htaccess in the root directory to see if you can find entries for webp replacement between the LiteSpeed markers.

What do you mean by that?

Assuming you are right when it comes to the generation, I don’t understand why this would stop working all of a sudden? How can you explain that?

@serpentdriver I hear what you are saying. But I’m using ShortPixel to create the webp images and LiteSpeed to serve them.
It is in fact ShortPixel that creates them.
I’m using this in wp-config which makes ShortPixel create them with double file extensions for LiteSpeed:

define('SHORTPIXEL_USE_DOUBLE_WEBP_EXTENSION', true);

I have webp generation turned off in LiteSpeed.
The webp images are created before hand, not on the fly. My example file listing above was the result of:

ls my-image*

And as I said this worked before and has worked for years. Something changed in LiteSpeed or ShortPixel to break this. And it’s not only on my site.

@serpentdriver Thanks for the suggestion. But ShortPixel creates and writes the webp to disk in the same directory as the other media files. Only this stopped working a month ago.

It can look like this:
my-image-100×150.jpg
my-image-100×150.jpg.webp
my-image-1024×1536.jpg
my-image-1024×1536.jpg.webp
my-image-300×450.jpg
my-image-300×450.jpg.webp
my-image-600×900.jpg
my-image-600×900.jpg.webp
my-image-768×1152.jpg
my-image-768×1152.jpg.webp
my-image-800×1200.jpg
my-image-800×1200.jpg.webp
my-image.jpg
my-image.jpg.webp

Thanks @conschneider for explaining this. It’s not the notion you get when reading the update notice in the Stripe dashboard:
“You’ll be able to roll back to your previous API version for the next 72 hours. Follow our upgrade guide to test the new changes.”

But if it’s like you say it is, it’s best to always update to the the latest version in case the plugin starts using a newer version that you otherwise don’t have on the Stripe side. The current version in the plugin seems to be 2020-08-27 but it has been working fine anyways.
I was on 2018-09-24 in Stripe dashboard, now updating to 2022-11-15.

Kind regards,
Ben

After updating to the latest LiteSpeed cache plugin I’m not seeing this in the logs any longer.

@khungate Thanks for your response.
I flushed the litespeed cache in Cpanel in LiteSpeed Web Cache Manager. But I’m still seeing it in the logs.
I’m waiting for a response from my webhost.
For caching I’m using LiteSpeed cache on a litespeed server and Redis Object cache.

@wordpressorgtimpeter I’m on LiteSpeed cache with REDIS and seeing the same thing. So it’s a more general issue it seems.

+1 on a fix for this. Thanks!

Hi!

Having all these deprecated warnings sprayed in the logfile makes it hard to debug other issues. Could you please prioritise this issue? Also as it affects so many people and could potentially save some energy by not filling disks and using extra processing power to no purpose.

Thanks!