Plugin Support
qtwrk
(@qtwrk)
for plugin , if you have a image file like something.jpg, then it will look for something.jpg.webp if this file exists and loaded by supported method , as <img tag , then it will replace it
the workaround rewrite rule
^(.*).(jpg|jpeg|png|gif)$ $1.$2.webp
the $1 referenced to file name , and $2 referenced to jpg/jpeg/png/gif , so it is also looking for something.jpg.webp
the way you name it like something.webp may not work with it
Plugin Support
qtwrk
(@qtwrk)
@bandreas3 my apologize for any inconvenience or uncomfortable you may experienced , as many member of team are not native English speaker, sometimes the language barrier could give wrong sense
if you still have webp issue , please create a ticket here , we will investigate further
-
This reply was modified 3 years ago by
qtwrk.
-
This reply was modified 3 years ago by
qtwrk.
It seems to have been resolved because the Insights warning has disappeared! I’m not sure how to manually verify it, but I imagine that if the notice to publish the images in the next-generation format is no longer appearing, it’s because they are now being recognized as such. Thank you for your help, @serpentdriver .
By the way, I have a question. The technical support from my hosting service recommended making changes in the “WebP Attribute to Replace” field, but of course, they mentioned that it would require payment for their configuration work. Would it have worked just as well as the solution you provided, @serpentdriver ?
In the second screenshot I posted in my first message, it’s the third field from the bottom.
Leave these settings for “WebP Attribute to Replace” field untouched. There is no need to change these settings.
I’m glad I decided to ask for help here instead of paying for the “technical support” from my hosting provider. I can see they were misleading, and I would have paid for nothing. Once again, thank you for your assistance @serpentdriver
I’m glad to have helped you. 🙂