lozula

Ok, so I added it at the start of the wp_config file and now the Autoptimize files are in an entirely separate folder under /wp-content/AOCache/

However, clearing the WP Fastest Cache is still clearing this cache folder, even with

add_filter(‘autoptimize_filter_main_hookpagecachepurge’,’__return_false’);

in my functions.php file.

Do you have any other suggestions I could try?

As a workaround I will move the AO cache directory using

define(‘AUTOPTIMIZE_CACHE_CHILD_DIR’,’/resources/’);

I added this to my wp-config.php file, is there anything I need to do to make AO see this change?

Hmm, that is possible. It is new behaviour though because I have been running it for ages with no issues. I will raise an issue on their side.

Ok wait, I tell a lie. I had that filter already in my functions.php file, but WP Fastest cache is still clearing the AO cache even with it there. Any idea why that would be?

Frank, thank you so much for the fast reply. I had a feeling there was a filter for this but I couldn’t remember where I read about it. I’ve implemented that and it’s resolved the problem.

Normally this isn’t an issue, but somehow cloudflare had cached a version of a page with reference to a missing css file, and I’ve been getting e-mails from people about my site being broken. This should fix it – thanks again!

Laurence

Hi @coreyk

I did search for that string, as well as just “autoptimize” in general, following a discussion with Frank of Autooptimize. None of the code in my theme files or other plugins calls AO, it’s only found in the AO plugin itself.

In addition, when I disable cache enabler, AO no longer clears the cache when I update a page. I installed a different caching plugin, which also doesn’t cause the cache to clear when I update a page. So I can’t see how it can be anything other than something in Cache Enabler causing this to happen, but I have no idea how to troubleshoot and figure out what that would be

I switched caching plugins and the AO cache no longer clears unexpectedly. So that’s good enough for me ??

Ok, I searched my whole site, from the root directory up, for autoptimizeCache::clearall(), and even just autoptimizeCache.

The only reference to it is in the AO plugin directory.

Then I deactivated Cache Enabler. With Cache Enabler deactivated, the cache does not clear when I update the page. When I reactivate Cache Enabler, the AO cache clears when I update the page. The Cache Enabler cache also clears, even when I have it set not to. So I guess the fact that Cacne Enabler is clearing it’s cache is triggering AO to do the same.

Unfortunately the Cache Enabler folks can’t replicate this behaviour. I might have to find another caching plugin.

Hey Frank,

Thanks very much. I use very few plugins to try and keep the site pretty tight, and use a Genesis based theme.

I’m hosted on Flywheel, who have their own Varnish based caching solution.

Do you have any tips for how I might go about figuring out where to look to see what’s triggering the cache clear? It’s kind of frustrating that the AO cache clears whenever I update a page, and weird that it doesn’t do it when I update a post!

Thanks

Laurence

You are absolutely correct, updating a page is for some reason causing the Autoptimize cache to be purged. I had never noticed this before.

@optimizingmatters – any thoughts as to why this might be happening?

I use autoptimize, but I don’t believe it clears the cache unless I specifically tell it to. The only other caching is done by my host (Flywheel), so I guess they could somehow be triggering the cache clear when I update a page? Is that possible? It’s just weird that it doesn’t trigger it when I update a post.

None of my other plugins are related to caching or would have any way to clear the cache that I can see (I run a pretty small number of plugins on the site)

• This reply was modified 5 years, 6 months ago by lozula.

Hey Florian!

Yep, seems to work fine. Running on my live site with no issues. I also tested it with the Chrome Beta with the lazy load flags enabled, and the page performs as expected with the browsers lazy load taking over the lazy load functions ??

So all looks good to me!

Laurence

@hydn I use the cache everything rule for the /wp-content/ folder.

@hydn just follow the instruction on the blog post here:

https://github.com/cloudflare/worker-examples/tree/master/examples/edge-cache-html

No worries, and no rush Florian. Just wanted to let you know I’m happy to help ??