iSaumya

Hi,
Can you please share the error so that we can see what error it is causing? Without knowing the error, it is hard to make a guess.

Thank you so much for all the love <3

That was the plan. Not sure what the Optimole team has in mind about this now. As this is no longer needed since the introduction of cache rule.

I’m sure the team is looking into it.

Hi you can use the cronjob to purge cache. The option is there inside the plugin settings.

So sorry to hear about such an experience that you had. Also, glad to hear that your issue has finally been resolved.

Hi,
Since the introduction of the Cache Rule, the worker is not needed for Cache operation. Yes, the worker is super powerful and can do many amazing things. But it is no longer needed for cache operations.

Hi,
It seems you have not enabled the Cloudflare Cache integration inside the plugin settings. Once you enable that the plugin will auto-add the cache rules that will allow you to serve your pages from Cloudflare CDN.

Hi,
This plugin does not uses worker or worker KV instead it leverages Cloudflare Cache Rules.

Hi,
I think you need to select the last 20 options for the preloader to work. But you do have a good point. Maybe incorrect messaging in the plugin settings.

Hi,
Can you please share a screenshot of the page rule and the cache rule section from your Cloudflare dashboard?

Scott,
Your API Token Permission looks good to me. If you are using Cache Rules you really don’t need to use Worker.

Unless you provide your website URL and a way to test/reproduce the issues, it’s hard to replicate it and help your further.

I’m glad to hear you have found the main issue behind this.

CDN Cache Control tells Cloudflare how long to keep the item in the cache. So, even if it’s 304 it should get expired.