Full page caching

If you’re getting 404’s on the AO’d CSS/ JS, that implies the AO cache somehow was cleared (by clicking “save options & clear cache” or by some cronned job clearing AO cache -which AO does not do by itself- or another plugin calling autoptimizeCache::clearall() ) without your full page cache having been so.

The result; your cached HTML has references to non-existant AO’ed JS/ CSS.

The solution; making sure the AO cache does not get cleared OR clearing your CloudFlare page cache.

hope this helps,
frank

Thanks for the quick response, the theme is DIVI. IN divi i can see that it is indeed making use of autoptimizeCache::clearall() in the file: core/components/init.php at line 158.

It looks like this:

if ( ! function_exists( 'et_core_clear_wp_cache' ) ):
function et_core_clear_wp_cache( $post_id = '' ) {
        if ( ! wp_doing_cron() && ! et_core_security_check_passed( 'edit_posts' ) ) {
                return;
        }

        try {
         // some various other plugin rules
         // ..
         // ..
                if ( is_callable( 'autoptimizeCache::clearall' ) ) {
                        autoptimizeCache::clearall();
                }
        } catch( Exception $err ) {
                ET_Core_Logger::error( 'An exception occurred while attempting to clear site cache.' );
        }
}
endif;

So in my child theme…its very easy to rewrite et_core_clear_wp_cache.

In the edge caching scenario, what do you think would be the best way to rewrite it.

Also of note, in the code i can see references to wp-rocket and w3 cache having the ability to clear cache on per-post id basis, does your plugin have that ability as well? Ie something similar to: rocket_clean_post( $post_id ) or do_action( ‘w3tc_flush_post’, $post_id ) ect

Ah, Divi … see https://blog.futtta.be/2018/11/17/warning-divi-purging-autoptimizes-cache/

AO does not have a purge per ID, as optimized CSS/ JS can (and generally will) be reused on multiple pages.

The best way would be to stop Divi clearing AO’s cache entirely. I consider it a serious bug (based on a fundamental misunderstanding of what AO does) :-/

Interesting, okay I will make that adjustment in my child theme. That said, say divi contact form changes on an update. I’m assuming that after i make my child theme adjustment, that aupotimize will see the updated js and then create an new autoptimized file?

I’m assuming that after i make my child theme adjustment, that aupotimize will see the updated js and then create an new autoptimized file?

entirely correct ??

Can I ask you something @jiggaman ?
I assume you are doing cache everything with a page rule in cloudflare. But when you publish a new post cloudflare won’t clear the cache (for home and other archives). So how do you deal with it? Just manually clear all caches each time?