John Teague

I’d disable the Autoclear plugin while you fix any other issues, then activate after that.

CriticalCSS is very good at automating more advanced CSS issues. A lot of my clients use it, and I recommend it.

Just to confirm. I’m not affiliated with Autoptimize. I do use their products, and the Autoclear plugin is my own separate plugin.

So, it’s important to know that the Autoclear plugin is not an Autoptimize plugin. I created the Autoclear plugin for one purpose, which is to aid in prevent cache sizes from becoming so large they cause performance issues themselves. It’s purpose isn’t to mask over other optimization issues. The mobile scores are more strict about blocking assets than desktop. So I’d disable the Autoclear plugin while you sort out those other issues. Hope this helps.

Still attempting to work out some solution for this and I’ve got a call scheduled next week to discuss.I just wanted to let you know that I haven’t forgotten. Thanks for your patience.

Thank you fir the report. It appears we’ve finally figured out what causes this, which resides around certain conditions when object caching is set to override the max age setting. This can happen with certain web hosts and CDNs. I’m finishing a fix and testing it.

In the meantime disabling our plugin, completely emptying object cache from plugins or third party services and purging CDNs and the activating and setting the max allowable cache in our plugins settings page should resolve this. If that interim solution fails, disabling it and waiting on the update (about 10 to 14 as we wait for WordPress core update to land) should do the trick. Please let me know.

Thank you again for your patience. I understand how frustrating issues like this can be, especially when they only appear when under certain conditions .

Just when I thought I’d figured this out. It seems like there are a couple of situations where this occurs, but I appreciate the additional info.

Can you let me know if you have any other caching plugins installed, such as WP Supercache or WE Total Cache, etc. And who and what hosting package your using. This is usually caused by having those types of plugins containing cached versions of the site after Autoptimize has been cleared. Normally that clears all of your local site cache files, not just Autoptimize.

If you use a host that uses their own server side caching methods it can also cause this. The extra info may help me pin down exactly why that’s happening. Also, I’ll finally have an updated version of the plugin out by the weekend, and it will save the settings as soon as it’s installed, which should solve this.

Apologies for the issue. Thank you for reporting it.

I’ve added a a function to automatically save when first activated which solves the loop problem for certain cases. Thank you for letting me know. And your patience.

Awesome. So glad it’s resolved. Thank you for your help and for using the plugin.

Let me take a look at that possibility. That function is set within Autoptimize itself, but there may be a way past it. I’ve been thinking about incorporating our own cache deletion functionality. I’ll look into it and then report back. Thank you for your patience and help with diagnosing the problem. It’s one of those edge cases that’s been harder to get at the cause. But, I’ll stay on it.

Thank you Frank. Will do.

Thank you for the kind words. I’m very grateful, and glad you’re happy with it. Cheers!

I’ve reached out to Pantheon to determine if there’s a safe way to trigger a cache removal of their cache builds when autoptimize clear cache plugin is installed and activated. But I’ve not heard back yet. I just sent a follow-up to them and I’ll report back to you as soon as I hear from them.

For wow.js, there are a lot of reports of conflicts with other plugins as well. I’m not sure how to test against it, but the latest release of autoptimize plugin now triggers a cache deletion of w3 total cache and wp supercache plugin cache to prevent conflicts. and it appears to solve this issue.

Thank you for the detailed reply. I’m bringing some tests and attempting to isolate the cause, but this definitely looks like a bug.

In the interim, I’d recommend clearing all cache.

I suspect this may be related to certain hosted environments that aggressively cache, but that’s unsubstantiated. I’ll report back and/or release an update as quickly as possible.

Again, apologies for the the trouble and thanks for helping us with a solution.

I’m investigating this and appreciate the information in your reply.