digitalpoint

Maybe… I don’t see anything from skimming the code, but I didn’t go so far as to install it. Either way, the underlying issue does seem to only be an issue with some combination of multiple other plugins installed. One is making all notices dismissible, and the other is then hiding dismissible notices.

Great!

I was going to install it and try to figure out why it thinks that particular page is a notice, but I might just let this one go considering it’s been half a decade since it’s been updated (for WordPress 3). 😂

There shouldn’t be a reason coming from this plugin. If you have guest page caching enabled, putting the site into development mode (on Cloudflare’s side) will bypass the edge cache for you. You can also just purge the entire cache if you think it’s a case where some stuff is in Cloudflare’s cache.

But fundamentally, there’s really nothing this plugin does that changes files or structure or anything along those lines. The exception to that would be the Pro version of this plugin does allow you to store images in a Cloudflare R2 bucket, so they wouldn’t exist locally in the filesystem, but if you aren’t doing that with the Pro version, then it’s not that.

Are you able to dig into the specifics of what’s failing? Like is an image missing via the web request, but exists in the expected place in the filesystem? Should be able to narrow down if it’s a missing file, or the web server looking in the wrong place or something at least.

When I test that URL, I get the expected result of: cf-cache-status: HIT

Have you tried a new Incognito window to make sure there isn’t something in your browser session that could be making it fetch a non-cached version? Normally that would just be if you were logged in, but there’s a few other things that could cause it (like a guest leaving a comment on a post).

Normally, EXPIRED means exactly that (that there is a cache available in Cloudflare’s server, but the cache is expired). I did see some strange headers in your site… for example something is setting a directive saying the page expired in 1981 (that header isn’t coming from this plugin).

It’s under Public Page Caching. There is a toggle to enable it.

It’s done with a single Cache Rule that tells Cloudflare to consider all requests as cache “eligible” (eligible doesn’t necessarily mean all requests will be cached). Then the plugin can make the determination for which requests should actually be cached and passes that determination along to Cloudflare by adding the appropriate Cache-Control HTTP headers.

APO probably made more sense for Cloudflare to rollout at the time, because Cache Rules weren’t a thing back then. Today, APO doesn’t make a ton of sense as a subscription (probably why they haven’t updated their APO plugin in a very long time).

I haven’t tested that Worker code (I also don’t have LiteSpeed installed anywhere), but I don’t see anything in there that would interfere with this plugin.

If your Cloudflare zone is on a paid plan (anything except “Free”), you may want to look at Snippets. They are lightweight Workers that have no per request cost (Workers are free for up to 100,000 requests/day, but there’s a cost after that). That’s fairly simple Worker code, so should work just fine as a Snippet.

Going to go ahead and close this one out (feel free to reopen or continue discussion if anything else comes up). I finished what I wanted to finish for the Turnstile stuff, so I’m shooting for a late Monday next version release, which will include the thing for Image Transformations on sites outside of the root domain.