Hi @pantsman28,
I am not related to this plugin, but I use it often. I saw the URLs that you have shared and even though **GD** and **Imagick** are available, they can’t be used because they are **”compiled without WebP support”** – which means that they can’t convert images to webp.
And cwebp is not working because **”exec() is not enabled”** – which means it is not possible to execute cwebp binary.
Thanks for the reply, Actually trying to get the hosting company to acknowledge that the cwebp is not enabled. How would you go about doing this?
The hosting service said they won’t enable this as its a security issue.
Found the below code at
But no mention as to where it gos? .htaccess file?
# WebP Express rules
# ——————–
location ~* ^/?wp-content/.*.(png|jpe?g)$ {
add_header Vary Accept;
expires 365d;
if ($http_accept !~* “webp”){
break;
}
try_files
/wp-content/webp-express/webp-images/doc-root/$uri.webp
$uri.webp
/wp-content/plugins/webp-express/wod/webp-on-demand.php?xsource=x$request_filename&wp-content=wp-content
;
}# Route requests for non-existing webps to the converter
location ~* ^/?wp-content/.*.(png|jpe?g).webp$ {
try_files
$uri
/wp-content/plugins/webp-express/wod/webp-realizer.php?xdestination=x$request_filename&wp-content=wp-content
;
}
# ——————- (WebP Express rules ends here)
How would you go about doing this?
Usually I switch to a different plugin if there are no options available, usually EWWW Image Optimizer.
The hosting service said they won’t enable this as its a security issue.
Yes, a lot of hosting providers disable exec() because it could be used to executing any other binaries as well.
But no mention as to where it gos? .htaccess file?
These are nginx rules so these should go in nginx config file, not htaccess. But since you don’t have any available converter options, adding these wouldn’t help anyway.
