Oh, thanks for reporting! The bug simply needs to be fixed. I shall fix it. I’m expecting the next version to be released within a week. If you don’t want to wait, you can edit /home2/mohammadreza/public_html/wp-content/plugins/webp-express/vendor/rosell-dk/webp-convert/src/Converters/Imagick.php and change $im::queryFormats() to $im->queryFormats(). And you need to make that same change in /home2/mohammadreza/public_html/wp-content/plugins/webp-express/vendor/rosell-dk/build/webp-on-demand-2.inc (search for “$im::queryFormats()”)
Thread Starter
nwdo
(@nwdo)
Quick reply! I’ll just wait for the update. Thank you so much!
I have just released 0.9.0. It should work now!
Thread Starter
nwdo
(@nwdo)
Well the bug is fixed but now it says that the iMagick was compiled without WebP support. I Think it’s from the server side, but i don’t know what should i do. Is there anything i can do to fix it?
By the way, I needed to deactivate jetpack plugin to use Webp Express. Just wanted to report that.
Thanks for reporting the jetpack issue. I have added it to the issue queue: https://github.com/rosell-dk/webp-express/issues/127.
As to what you can do. Well, sounds like you are in the “No converters are working out of the box” situation, which is described in the FAQ: https://ww.wp.xz.cn/plugins/webp-express/
As for compiling Imagick with webp, there are some instructions on the webp-convert wiki: https://github.com/rosell-dk/webp-convert/wiki/Installing-Imagick-extension. If you are on a shared host, you can try to write to them. If that doesn’t work, look at the other options in the “No converters are working out of the box” section in the FAQ
Regarding Jetpack:
If you install Jetpack and enable the “Speed up image load times” then Jetpack will alter the HTML such that images are pointed to their CDN.
Ie:
<img src="https://example.com/wp-content/uploads/2018/09/architecture-q30.jpg">
becomes:
<img src="https://i0.wp.com/example.com/wp-content/uploads/2018/09/architecture-q30.jpg">
Jetpack automatically serves webp files to browsers that supports it using same mechanism as the standard WebP Express configuration: If the “Accept” header contains “image/webp”, a webp is served (keeping original file extension, but setting the “content-type” header to “image/webp”), otherwise a jpg is served.
As images are no longer pointed to your original server, the .htaccess rules created by WebP Express will not have any effect.
So if you are using Jetpack you don’t really need WebP Express?
Well, there is no point in having the “Speed up image load times” enabled together with WebP Express.
But there is a case for using WebP Express rather than Jetpacks “Speed up image load times” feature:
Jetpack has the same drawback as the *standard* WebP Express configuration: If a user downloads the file, there will be a mismatch between the file extension and the image type (the file is ie called “logo.jpg”, but it is really a webp image). I don’t think that is a big issue, but for those who do, WebP Express might still be for you, even though you have Jetpack. And that is because WebP Express can be set up just to generate webp’s, without doing the internal redirection to webp (will be possible from version 0.10.0). You can then for example use the Cache Enabler plugin, which is able to generate and cache two versions of each page. One for browsers that accepts webp and one for those that don’t. In the HTML for webp-enabled browsers, the images points directly to the webp files.
Pro Jetpack:
– It is a free CDN which serves webp out of the box.
– It optimizes jpegs and pngs as well (but note that only about 1 out of 5 users gets these, as webp is widely supported now)
Con Jetpack:
– It is a big plugin to install if you are only after the CDN
– It requires that you create an account on WordPress.com
Pro WebP Express:
– You have control over quality and metadata
– It is a small plugin and care has been taken to add only very little overhead
– Plays well together with Cache Enabler. By not redirecting jpg to webp, there is no need to do any special configuration on the CDN and no issue with misleading file extension, if user downloads a file.
Con WebP Express:
– If you are using a CDN and you are redirecting jpg to webp, you must configure the CDN to forward the Accept header. It is not possible on all CDNs.
