PS the .webp version of the images are being created (ie if .jpg exists, there is a .jpg.webp version as well), they just don’t appear on site.
Hi @wattaman
It is possible that the file may still display as “.jpg” in your source but the mime-type is being served as WebP. I would probably recommend checking first in the Network tab of the Dev console to verify that the images aren’t coming through as WebP. If you aren’t seeing them as WebP in the mime-type there, then I would suggest checking out the WebP delivery documentation here: https://docs.ewww.io/article/119-webp-delivery. That document lines out what is needed for nginx delivery and specifically mentions that the images may still show as .jpg but are coming through as WebP (and how to confirm it).
If none of that resolves this for you, if you can share the system info from the support tab of the plugin settings, I can have a look at things and see if I can see what’s going on. You can share that in a pastebin link or to us directly at https://ewww.io/contact-us/
Alright, I’ve done the changes in the nginx, images show in the console as webp, although they still show as .jpeg in the page. So far so good.
However, I’d like them to load as .webp images as well, mostly because Jetpack CDN (that I also use) already cached the .jpeg versions and they won’t clear the cache to load the new ones. So, is there a way to use the .jpeg.webp img src (or backgrounds etc) after converting the images in bulk?
I’m not sure I follow… they are loading as WebP properly, but your Jetpack CDN cache has the JPG versions loaded? Do you mean you checked your site without Jetpack and if you turn it back on, it’s loading the jpgs? So, the issue isn’t that the images aren’t serving properly, it’s that the CDN has cached the JPGs? In that case, you would need to clear that CDN cache.
You could try the JS WebP option to see if that changes how the images are served and maybe triggers a cache refresh but…you definitely still want to clear that cache just in case.
Forget the CDN.
The issue is that although images ending is .jpeg.webp do exist (they have been created by the plugin), only images ending in .jpeg are being served by the website. And even though are actually WEBP images, as seen in the browser console, I’d like the website to use the .jpeg.webp as the IMG SRC. Hope this is easier to understand.
I have checked JS WebP and Picture WebP Rewriting.
OK, so there’s a lot going on here with your current setup that it might be best to start over. First, remove the nginx rewrites you added and clear your Cloudflare cache. I know you said to forget about the CDN, but if you are going to use Jetpack, it automatically serves WebP. As such, it doesn’t need local versions (which is what our plugin is generating). So you could remove all of this and just use that, unless it isn’t getting everything or you don’t want to use Jetpack.
If that’s the case, get rid of Jetpack and use EWWW just with Cloudflare. Cloudflare will operate as your CDN and you can use the JS WebP function of EWWW to serve your WebP versions through CF. That should function as you want (and again you don’t need those nginx rewrites).
I’m going to resolve this thread as I haven’t heard anything in a while. If you have further questions please feel free to open a new one!
