Turn off AO from commandline?

OK, so what I ended up doing was to move the autoptimize.php to autoptimize.php.save. Then WordPress deactivated it because the plugin file no longer existed.

Is there any way to get this back to normal or help provide more feedback. It would seem that 24 hours of calls from my machine to ao_speedup_cachebuster is not the most productive use of CPU time.

I believe this is due to an odd interaction between ao and another plugin (mediavine-create), but I’m not sure what.

i’ve had other people reporting this and it turned out they were using something (a plugin/ code snippet) that tries to auto-purge autoptimize’s cache? if so, can you deactivate that and try again?

if not; is there any reason why you suspect this could be due to “mediavine-create”? have you been able to confirm that is in fact the issue by deactivating that (even if only for a short time)?

and finally; if all else fails open up wp-content/plugins/autoptimize/classes/autoptimizeCache.php and comment out lines 365-367 so;

            $url   = site_url() . '/?ao_speedup_cachebuster=' . rand( 1, 100000 );
            $cache = @wp_remote_get( $url ); // @codingStandardsIgnoreLine
            unset( $cache );

becomes:

            #$url   = site_url() . '/?ao_speedup_cachebuster=' . rand( 1, 100000 );
            #$cache = @wp_remote_get( $url ); // @codingStandardsIgnoreLine
            #unset( $cache );

hope this helps,
frank

Thanks for the reply. I’ll be chatting with the mediavine folks today to see what may be causing this. Unfortunately, I won’t be able to shut of that extension, because it’s a key part of my blog.

Once I know more about it and if it’s still a problem, I will put the suggested fix in and let you know what the outcome was.

Sure ??

but:
* this is not a fix but an (ugly) workaround which would have to be re-done after each update of AO (the filter you tried should just work)
* it’s still unclear to me why you suspect it could be mediavine? ??

* this is not a fix but an (ugly) workaround which would have to be re-done after each update of AO (the filter you tried should just work)

Yes, I understand. This is why I’m first trying to understand why this is happening in the first place.

* it’s still unclear to me why you suspect it could be mediavine? ??

The times this happened (twice) was immediately after I updated the mediavine plugin. That plugin provides recipe cards for my blog (it’s a baking blog and therefore I can’t disable it…) and it is still under active development.

Thanks again!

OK, maybe check with the mediavine developers if they clear Autoptimize or a page cache (which AO sees upon which it purges it’s own cache) multiple times. If they do either, this would trigger AO to run the “warm cache” logic (to preload the cache) which is done using the “cachebuster”-request.

I installed the latest version of the mediavine plugin which had a note in the changelog:

FIX: Remove unnecessary Autoptimize clear on activate and deactivate

And that appears to have fixed this problem.

Thanks for your help!

great news, thanks for keeping me updated!

feel free to leave a review of the plugin and support here! ??

have a nice evening,
frank