Ashutosh

Cache Enabler should work fine with EDD. From the quick glance it looks like you have to exclude the /checkout page and some EDD cookies from being eligible for cache. The settings in Cache Enabler are about as simple as they get.

Note that persistent object caching is as important as page caching for sites with dynamic features like user login, ecommerce, profiles, etc.

A version will be created when a user agent/client/browser requests for that version. Most user agents support gzip and will pass that information in an Accept request header. So Cache Enabler will create the gzip (index-https.html.gz) and serve it to the user agent. If your site ever receives a request from a user agent that does not support gzip, Cache Enabler will create the plain version (index-https.html) and serve that. This way, a cache file is created only when it’s needed and it stays valid for the period defined in Cache Enabler settings.

I love this plugin so much and it’s sad to see it have almost no activity these days. Most support threads go unanswered. ??

I don’t believe so. I haven’t used reverse-proxy caching in nginx but I have used fastcgi cache and performance was as good as any WordPress cache plugin, and arguably better. nginx already has excellent caching modules, so you should use them to leverage server level caching instead of using WordPress plugins.

I have since switched from nginx to caddy, which doesn’t include a caching mechanism in the default setup, so I’m using Cache Enabler and am very happy with it. Cache Enabler works reliably and has so far avoided feature bloat, which is a huge issue with several popular WordPress plugins these days.

It will work, but php will be used. The code is necessary if you want php to be entirely bypassed for cached pages. This applies to whatever web server or proxy you’re using, be it apache httpd, nginx, caddy, etc.

I am not associated with this plugin, but just wanted to chime in that it works well with nginx out of the box. If you want to bypass php processing by WordPress entirely for cached pages, you can follow Cache Enabler’s official guide: https://www.keycdn.com/support/wordpress-cache-enabler-plugin#nginx

I have personally used it with nginx and am now using it with caddy.

Honestly, a bit concerning that no one seemingly checks or maintains this plugin for months. I understand that this is a simple and mature plugin, but checking the plugin for a couple hours every month and updating the “Tested up to” value would let users know that it has not been abandoned.

Hey Kavya,

I tried removing the font with the Create Block Theme plugin, but it didn’t show Instrument Sans. I ended up “fixing” the issue by creating a child theme, and going through theme.json to remove all the sections mentioning Instrument Sans.

Fixed

Thank you for the links and for the excellent plugin! Your article on the statistics clarified my doubts.

thank you. an option to keep the events disabled/inactive would be nice, but it’s good that they have negligible impact.

many thanks for the explanation and links!

Thanks Tom! That makes sense. I recently found out that WordPress also has “hidden” sizes for 1536×1536 and 2048×2048, which I have now disabled. Wonder what other sizes are there…I’d really like WordPress to not create different image sizes on my behalf.

FIXED.

Oh no, I looked through the forum and looks like many have this problem! ?? Thankfully I only have one site to manage, so it wasn’t too much work to switch back to 5.6.4. I will look in the threads for any fix. I feel major releases are usually best postponed until after the “general holiday season”.