richarddegoffau

Hi @extremecarver

>>?I think I found the problem about the JPG vs jpg. your plugin picks up JPG for conversion

that’s correct, but I assumed uppercase extensions cannot occur in WordPress, because WordPress converts the filenames to lowercase when uploading.

I’ll solve this as soon as possible so that also uppercase extensions are handled correctly.

Hi @extremecarver ,

Thank you for your valuable input.

>>?but the website tells the browser to download the converted one – and it cannot fallback to the original image – then this is not acceptable

Let me first explain something: the functionality is: on the first request to “/?fw-webp-avif-ondemand=all” – the original image is hardlinked/copied to the cache folder to serve as an immediate fallback, while the conversion is queued. When this image does not exist (and it seems it doesnt in your case) – there is something wrong with the nginx rules. (maybe conflicting?)

>> if ($http_accept !~* “image/avif”)…

I tried to avoid if’s in nginx – as they are evil according to the nginx docs ;).

But I’ll try to use your feedback to improve the nginx rules in the next few weeks.

Hi @julien66 ,

>>Your webhosting does not support AVIF conversion
You can ask your hosting provider to support ImageMagick with AVIF support.

>>WebP/AVIF image request failed, make sure the site can connect to itself on abc.com
This is not necessarily an error, but only a warning. Can you check your site health page to determine loopback requests are working?

You can also check the plugin settings page. When you see #converted images > 0 – the plugin is doing its job!

Hi @extremecarver ,

Thank you for your feedback.

>>Somehow this plugin changed the source from .jpg to .JPG when it unsuccesfully tried to cache them in webp or avif.
I can ensure you that it’s impossible that our plugin has changed the source from .jpg to .JPG – that has to be caused by another plugin or piece of code.

The WebP/AVIF converter only writes images to the cache directory, and serves them (with a fallback to the original image). But there might go things wrong, for example because of:
– max execution time / memory limit too small (this might cause large images cannot be converted)
– conflicting nginx rules (it’s difficult to advise here because many sites have their own unique configuration – in which you should solve the conflicting rules).

Can you paste your nginx-configuration here to be able to help you further?

Hi @stefacchio,

Thank you for your feedback.

In some cases the simulated WebP/AVIF request fails because the site cannot connect to itself (which is common in docker configurations). Can you check this first? (you can check the loopback-requests on the health page of WordPress)

But of course something in your nginx configuration can also go wrong. Can you share your full nginx configuration so I can take a look what might go wrong?

(Our rewrite rules should work with a default nginx configuration.)

• This reply was modified 1 year, 8 months ago by richarddegoffau.

Hi @tlozano ,

How did you upload the files with local characters? As wordpress replaces all local characters with “ascii” characters in the media library.

The uploaded file “children-playing-ni?os-jugando-río.jpg” becomes “children-playing-ninos-jugando-rio.jpg”, and works in my installation.

Hi @enumis ,

I’m very sorry to hear that. Unfortunatly, I cannot see what might cause the problem without further information. Are you willing to share a screenshot of our plugin settings page?

The plugin works out of the box in <span style=”text-decoration: underline;”>default</span> WordPress installations on Apache. However I cannot guarantee to works in <span style=”text-decoration: underline;”>any</span> installation (no developer can) as there might be other plugins which are causing issues. I hope you understand?

Hi tlozano,

Thank you for your feedback and support! I’ll take a look at the images with special characters. Of course that should work too.

I’ll message you as soon as I have more information about this issue.

Hi @andrelauret23,

What do you see on the plugin settings page? Any messages?
It seems the nginx rewrite rules are not working properly, but I don’t see why yet.
Does the directory “/wp-content/cache/fastware-webpavif” exist?

Hi @andrelauret23,

Did you also add the lines in the http section?

map $http_accept $webp {
    default ".nonexisting";
    "~*image/webp" ".webp";
}

map $http_accept $png {
    default ".png";
    "~*image/webp" "";
}

map $http_accept $avif {
    default ".nonexisting";
    "~*image/avif" ".avif";
}

Hi @japenz ,

I added support for GDlib/AVIF to the plugin, but this will still not work in some distributions by default (I tested Debian 11) without recompiling gdlib manually. GDlib seems to support avif (the imageavif function exists) but generates always a file of 0 bytes. However on Alpine and maybe other distributions it should work.

Can you let me know if AVIF works for you now?

>>I have the similar error message
I found an error in the loopback test to itself. This should be fixed now in the latest version.

>>I’m waiting for GD: AVIF image support, then I’ll be all over it
I agree this would be nice – I’ll test again with GD+AVIF to see if I can use it in this plugin.
(but the last time I tried I ran into this bug: PHP :: Bug #81217 :: imageavif() fails – Segmentation Fault or No codec available)

Hi @japenz,

>>Any idea what I’m doing wrong?
This message doesn’t always mean something is wrong, but means that a test request from the site to itself (loopback) doen’t work. In that case, this warning is shown. This can be caused by many reasons (firewall, wrong siteurl, running within docker etc).

>>Any chance you might add GD: AVIF image support in the future?
Yes, in fact we have already tried AVIF with GD, but on most platforms: AVIF conversion with GDlib doesn’t really seem to work – despite GDlib seems to offer support, and the imageavif method exists. So we’ve not added AVIF conversion with GDlib to our plugin yet. But we will likely do that in the future.

• This reply was modified 1 year, 10 months ago by richarddegoffau.

Hi @tlozano ,

Glad to hear it works. I’ll add a cron-checker on the config page to see quicker what the problem might be in case it doesnt work.

Hello @stillfree,

You can find the generated rewrite rules in /wp-content/.htaccess.
I also copied them for you on https://pastebin.com/fRyWQdJu.

Is mod_headers installed & activated?

The rewrite rules are automatically generated, so no need to install them manually.

Can you give more details on what exactly is not working?