adamewww

OK, Shane had a chance to look at it and it looks like the fix is going to have to be on their end and is essentially what you did. From what he saw (and from your temp fix), it looks like they check for document.arrive, which exists because we add it, and then a few lines later use e.arrive. Shane removed the jQuery bit on our end, but we’re not certain it’s going to work since, again, they are looking for something that is going to exist. So, that having been said, you can try the updated version of our plugin that you can get from here that Shane just pushed out but more likely than not, it’s not going to change much.

Quick question: Do you know if Hestia is including a different version of jQuery, or is it the stock WP version?

Hi therealgilles,

I checked with Shane on this and he said there might be a way we can modify the version we include to ignore jQuery, even when it’s available. He’s going to look into it and if something comes of it, let us know.

I think at this point I’m probably going to suggest two things, the first being to try a different thumbnail regenerator, as that one hasn’t been updated in 5 years unfortunately. The second being, if that doesn’t work, to contact us directly so we can look more deeply into it: https://ewww.io/contact-us/

Hi kinghill,

We prevent the image editor from generating new versions of images except in specific instances. However, there is an override that you could use to tell the plugin to “backoff.” Editor Overrite

Hi Pankaj,

Have you checked the mime-type in the network tab of the dev console? If that is still showing as the original, I would recommend having a look out our WebP delivery documentation about this: WebP Delivery

Hi nick1999,

It looks like there could be a couple of things going on. First, I’m not seeing many, if any of your images as WebP. Our plugin checks to see if the webp version is smaller than the original, and if not, won’t create it. But I am seeing that some images have a WebP version available, but it isn’t displaying it. So, more likely than not it has to do with how you are trying to deliver the WebP images. I would recommend having a look through our WebP delivery doc to help with this:
WebP Delivery

We received your support ticket and will respond through there.

Hi Sid,

Those don’t look like our WebP images. It looks like they are coming through Apache pagespeed which also generates webp.

Can you verify that you don’t have another plugin generating webp?

If you have further questions, can you please contact us via our support: https://ewww.io/contact-us/

To clarify, do you want to delete all images that were optimized but not delete the ones that aren’t? There really isn’t a quick way to do that, if that is what you mean. Or do you mean you want to un-optimize your images? If so, I’m afraid you can’t. You could restore the originals if it has been less than 30 days but once an image has been optimized, it is optimized.

Please feel free to contact support at https://ewww.io/contact-us/ with any further questions you may have.

Hi Nick,
Can you please submit your question from our contact page and please include your debug information: https://ewww.io/contact-us/

Thanks,
Adam

As Gal pointed out, your exec is disabled. You can enable exec or you can use our cloud plugin. If you have further questions, please submit them via our contact page (see sticky on these forums): https://ewww.io/contact-us/

Thanks,
Adam

Hi scamdenis,

You have to have exec() enabled on your server or the plugin can’t work at all, unless you use our cloud plugin which is subscription based. Your webhost may have disabled it or something has, so if you can, enable exec() and it will work. Or, if you would like, we can look further into this with you if you send the debug information from the Support tab to our support: https://ewww.io/contact-us/ but really there isn’t much that can be done unless that is enabled.

Thanks,

Hi Sally,

It won’t generate webp images if they are larger than the original image as it’s not going to work any better or faster (even if you re-optimize). If you would like to force it to generate webp images, you can do that. Should you need assistance with that, please contact us via https://ewww.io/contact-us/

Thanks,
Adam

One other thought… you could just delete the webp image. The plugin will then skip any further generation (unless you are using force webp).

Thanks,
Adam