Cache corrupts shotly after clearing entire cache

Hi,
Thanks for sharing the broken site. After looking at the console log, I can see that the issue is coming from some plugin which is using some wired wp-content path. Basically the CSS from that plugin/folder is throwing 404 and as a result you see the broken page, Screenshot: https://i.imgur.com/kAXVeT6.jpeg

URL:

https://pkvministries.co.za/twk-wp-content/uploads/uag-plugin/assets/1000/uag-css-1469-1699130388.css?ver=2.9.0

This is the cause behind all of your issues. I have no idea from where this twk-wp-content is coming from. It seems like this is happening due to some optimization plugin that you are using on your website which is generated critical CSS and then deleting the older filers causing 404.

I would highly recommend you to remove that plugin and instead switch to Perfmatters which is a million times better plugin for handling optimizations.

we change the path of wp-content to xxx-wp-content as a security precaution and define it in wp-config.php. We’ve been doing this on all our sites for over 6 years and I don’t think that’s the problem. Our test site https://test.pkvministries.co.za (which is a duplicator clone of the live site), also has this setting but not the caching problem.
https://prnt.sc/LV9CU4p3Sve0

I don’t think it’s that, if it were the cache should not work ok for a while after clearing it.

Well this is just weird. Seems that the CSS file required has changed, and cloudflare still points to the old one. Clear the cache and its fixed, with cloudflare pointing to the new one, and then bam after a while it points back to the css that does not exist anymore. Then the page loads corruptly. Solved it by manually duplicating the new css and renaming it to the old css Cloudflare is looking for. Documented here in case anyone ever sees that strange bug. No idea how this happens. Anyway, site loads now even with Cloudflare Super Cache enabled.

@isaumaya, unless you want to add anything can mark it as resolved. Finally.

Changing the path wasn’t the issue. The issue was, you have a plugin, that is creating crtical css and deleting old critical css file. Read my last reply. I’ve explained it there. I asked you to disable that plugin which was generating the critical css.

Yes, that is why, I suggested disabling that plugin that is adding the crtical CSS and switch to a plugin like Perfmatters for doing the same so that this does not cause the problem as this plugin adds the critical CSS inline on the page HTML.