Alternative WebP Rewriting kills site

Check your error logs to see if anything shows up there. Ask your webhost if you don’t know where they are.

Try this: https://downloads.www.ads-software.com/plugin/ewww-image-optimizer.zip

One of the regexp patterns was being too resource hungry and could have been causing your issue.

Hey,

That seems to have fixed the white screen issue, so that does seem to have been the issue.

Images don’t seem to be loading as WebP however, we use Cloudfront and S3 for our images, is that a problem?

I’ve also found a problem with the plugin, it seems to be adding this “?” before characters.

This only happens when alternative WebP Rewriting is enabled.

Please post a link to one of the pages where you’re seeing the odd characters.

If you’re using S3, you need to ensure that the webp variants actually exist on your S3 bucket. If you optimized all your images prior to enabling the WebP conversion, you’ll need to re-optimize them all again.

You can see if here:

https://technutty.co.uk/2015/05/14/footage-gears-war-remaster-for-the-xbox-one-leaks-online/

As for if WebP exists, yes it does:

You can see with this image there is a WebP version:

https://dyb74sw4cpb2o.cloudfront.net/blog/wp-content/uploads/2015/05/i3xNxRke2h5Wz-759×500.png.webp

But it shows this:

https://dyb74sw4cpb2o.cloudfront.net/blog/wp-content/uploads/2015/05/i3xNxRke2h5Wz-759×500.png

Yeah, there’s no way for EWWW to know if the CDN has a webp version, so it will likely fail in this case. I’m not sure how some of the other CDNs work, but Cloudflare is a transparent proxy, so I hadn’t considered what would happen if the images were not local. I’ll have to give that some thought and see what we can come up with.

Had a thought, does your site also keep local copies of those images?

We do for some, however we archive to Amazon S3 every year. So about 2 years of content doesn’t.

I’ve had a thought that would at least enable webp for the images that are local. I’ll let you know when I’ve got something ready to test.

Was also trying to look a bit deeper into the ‘special characters’ issue, and I’m getting a 403 on your site…

The special characters issue will be fixed in the next release.