Additional, the error code “3221225477” / 0xc0000005 is logged. Can’t find anything useful on Google yet…
Help is appreciated.
could you check the php errorlog?
frank
Hi Frank, there are no errors in the PHP log at all at that time, that’s the weird thing.
There are other logs from a time ago, so the PHP logging seems to be working.
It is a bit random, it happens ~80% of the time.
I see … some more questions:
* do you get the error immediately, or only after some time (10s or more)?
* and when you get through (20% of times), do you see a list of titles of autoptimize-related blogposts under “futtta about autoptimize”?
frank
– The error appears after ~5 seconds.
– Sorry, did not notice. And it’s not working now.
As your plugin was not working for me I’ve installed W3 Total Cache which does the job for me as well.
ok, bit of a gamble, but the problem might be with the code fetching those blogposts (although they’re stock wordpress fetch_feed calls).
so download the latest AO version from GitHub (soon to be 2.0.1) here and then use this code (which hooks into AO’s API) to disable the HTTP-calls;
add_filter('autoptimize_settingsscreen_remotehttp',__return_false);
frank
Where should I put that “add_filter”?
you could use the code snippets plugin for that (your -child- theme’s functions.php would be an alternative, but upon theme-updates the code would get overwritten).
but do update to the GitHub version, as the filter is not in 2.0.0.
frank
When activating 2.0.0:
Plugin could not be activated because it triggered a fatal error.
Sorry, I already switched to another plugin, may be you want to keep this issue in mind if it occurs again with somebody else.
Sorry, I already switched to another plugin, may be you want to keep this issue in mind if it occurs again with somebody else.
no problem, except for the frustration of not being able to pinpoint & fix this š
When activating 2.0.0:
Plugin could not be activated because it triggered a fatal error.
that was the github-version indeed? anything about that fatal error on the screen or in the php error-log?
frank
Yes I understand your frustration, sorry, but I’m super busy atm.
There is nothing in the PHP error log. Last error log is from 16 December.
May be it’s because of some other plugin I’ve installed.
sorry, but I’m super busy atm.
no problem. if you ever do have some time to help me hunt this down, let me know! š
frank
