Theme broken sometimes, had to deactivate plugin

Those are “file not found” errors vnpotato, something must be removing the AO cache without all page caches getting cleared (and you likely don’t have the “404 handler” active neither).

If you (a) enable the 404 handler and (b) make sure the page cache(s) is (are) always cleared when the AO cache gets purged (could be a plugin or theme, Divi is a known culprit) then this will not happen any more.

hope this clarifies,
frank

thanks for the reply.

here is the thing , we also have CLoudflare CDN that is cleared/syndicated with WP Rocket clear cache.
the easiest thing would be if AO clear cache will be integrated with WP rocket clear cache.

the way we do it now maybe causes trouble (clear Rocket cache and then clear AO cache manually, maybe in that time period some files are getting created and that causes the problem). that’s my assumption.

Clearing WP Rocket cache should be sufficient actually; AO indeed ‘listens’ to that and will clear its own cache automatically.

Make sure to also enable the ‘404 fallback’ though, if anything goes wrong with the cache clearing somehow that option ensures things don’t break badly.

so until now there was always a problem that occur in case we cleared cache only in WP rocket.
We then had to delete cache in AO, otherwise, things stayed broken.
Yesterday, things stayed broken despite we did the above.

What is 404 fallback option? I mean, does it fix the problem described? how?

Don’t see how not clearing AO’s cache would cause this problem I’m afraid; if you clear Rocket’s (a) AO’s _should_ be cleared automatically and (b) if that does not work no AO-files are deleted so those would not 404? is there any specific action done by you which *always* triggers this behavior?

the 404 fallback optoin sees AO create a “fallback” optimized CSS & JS file which can be used if the originally requested file is not found.

so in case there is 404 fallback – it takes the latest css version if it doesn’t find?

it takes the fallback one, which typically will be a copy of the CSS generated for the homepage right after the last cache clear.

ok, thanks for the help. will try this out

hello, getting back on this –
the “enable 404 fallback” was turned on.

So this is not causing the problem.

Hmm, in some cases the “404 handler” requires extra configuration on webserver level. Can you share your site’s URL so I can check?

any news vnpotato ?

No feedback so I assume this got fixed vnpotato ? Feel free to follow up if you still encounter issues!

have a nice day!
frank