Adaptive images folder empty

Hello, @defxs, thank you for your message!

The empty cache folder most probably shows that, at the time you viewed it, no smaller image sizes have been required to be created. This means that, at that moment, your website had not been accessed by a mobile device yet. The plugin creates the smaller image sizes it needs only when it needs them.

Now, I did check your website and it didn’t seem to have the Adaptive Images plugin enabled, so I couldn’t debug much. However, the plugin does not -yet- support the webp image format and it cannot work with a CDN like Shortpixel. So, maybe there is a lot going on there!

Let me know if I can help any further.

Cheers,
Takis

Hi Sorry,

I activated your plugin again.
I was testing some other things just for learning purposes.

When you look at the homepage at the section below “Kennisbank” you will see an umbrella picture that still is 1500px wide in it’s original source. It has not been sized and cropped.

The cache folder is also empty after visiting with my phone.
Can you check again?

Hello again, @defxs,

Thank you for the update!

Now, I see that the cookie the plugin is expected to set is indeed set, but hitting a debug url like https://mantelzorggoedgeregeld.nl/wp-content/uploads/2021/09/4.jpg?debug=true just shows the image and not the expected debug info.

I see that you are using NginX as your web server. This probably means that Nginx is not configured as necessary. In Apache the necessary configuration can be done automatically, but in Nginx one needs to edit the conf file manually. What you need to add there is mentioned in the success message presented to you when you save the plugin settings.

Is this something you could manage? If not, perhaps you need to contact your server admin for help!

Cheers,
Takis

Hello,

I Did indeed add your code for Nginx in the config file.
However, as soons as I did that Nginx would not start up again..

I am using Nginx on top of Apache. It’s a Cloudways hosted site.
Kind regards,
Mike

Hello, @defxs,

Sorry you had to go to all this trouble, but filtering image requests at this level is indeed tricky when there are so many combinations of servers and services in the picture.

What I mentioned in my last message applies to the case where Nginx is the main web server of your website! In your case Nginx is working in the same way as a CDN. So it is of no value here.

The last thing I can suggest is enabling the option CDN support in the plugin settings page. As it mentions there it is a bit experimental, but not in a way that anything breaks. It’s just the way that CDNs and, in your case, Nginx work. Maybe you can test it and see how it goes!

Cheers,
Takis

Hi Takis,

I tried that too.
I also let my host change the setting in Nginx so that it would let Apache handle images. That did not help either.

Unfortunate to see that it does work.
Your plugin is one handy extra feature to have.

Really sorry to hear this, @defxs!

All I can say is that combining all cases together is becoming indeed quite complex. Our next -long overdue, to be honest- update is cater for such cases, those that use a CDN or a caching server.

Thank you for giving all this a shot!

Cheers,
Takis