Image Optimization “Destroy all optimization Data” Question

wait a second , what do you mean by “not store backups” ?

please screenshot me your image optm setting…

I used the wrong term, I meant “Remove Original Backups” is ON

• This reply was modified 1 year, 3 months ago by Arnd Zanduino.
• This reply was modified 1 year, 3 months ago by Arnd Zanduino.

Attached is the screenshot

• This reply was modified 1 year, 3 months ago by Arnd Zanduino.

didn’t see any screenshot , but I assume you mean

Optimize Original Images = OFF

Remove Original Backups = ON

Image WebP Replacement = ON

if this so , you can just destroy it , the original files are not touched in this case

Thanks for the answer, I don’t know why the image didn’t upload into this thread, it looked like it was successful when I posted it.

Those are my settings. Thanks for the information and I’ll proceed to do that right now.

I believed your advice and went ahead. Unfortunately, your advice was bad. The process deleted all of the .webp files. Now I have to re-generate over 40,000 image webp files.

oh duang , I am sorry , I was focusing on your last question about what happens to original files when you destroy them … ??

I am re-creating the .webp files locally and uploading them back to the site. While doing this over the weekend, I noticed that even if the

Image WebP Replacement = OFF

is set, if I do a destroy data the process will delete all webp files again, even if they weren’t created by litspeed. This bug should be fixed.

yes, it’s by design , otherwise you need to go through each existing webp file , to check against database and file system , the destroy process will be slowed a lot , and also increase a lot of load for servers

we do not expect multiple image optimizations takes in place within same site

But if the webp setting is “off”, then no webp files should be deleted since the program should then assume that some other program is taking care of webp optimization.

well , think it other way around , what if user enabled it , get webp , then one day turn it off for whatever reason , and then one day decides to destroy ?

other image optm solution are probably using .webp as single extension, instead of double extension as we did though.

OK, I can accept the part with the single .webp extension vs. litespeed appending the .webp to the existing filename – that is uncommon and unlikely to be used by another product.

If the litespeed crawler, with webp enabled, crawls an image called “picture.jpg” and there is already a “picture.jpg.webp” present, will it overwrite the existing file or skip over it?

crawler doesn’t care if webp exists or not

if you enable webp option in image optm setting , crawler will do 2 requests separatedly

one with accept: */* header, one with accept: */*, image/webp

where the first request will trigger the plugin to use normal/original image URIs , like wp-content/uploads/2023/08/something.jpg because the request header didn’t express its support for webp image

the second request will go with image/webp header to tell plugin , explicitly, it accepts webp images , so plugin will replace image url to /something.jpg.webp if such file exists

so basically , for same page , you will have 2 versions of cache , one with webp , one without it.

I didn’t mean the crawler for going through the sitemap, but the image optimization crawler; i.e. the process that detects new images and going through the optimization and/or creation of .webp images.

• This reply was modified 1 year, 3 months ago by Arnd Zanduino.

it’s same case, depends on what is the request header they made , and plugin will respond accordingly

but if something is directly access to the image itself, then no , it will not be aware of webp existance

if something is accessing to your page with aforementioned header, it could get webp file links though.