Autoptimize & Memcached

I’ve heard this before once or twice, but have no idea why this would happen shanemarsh28 (I’m on Redis and have never had this problem) … what happens when you purge memcached?

Absolutely nothing – the trouble is I have to use the wp cli tools to flush the cache because I have other things using Memcache and the server loads get very high if I restart the whole instance.

Just a guess but I suspect the issue is being caused because the cache is persistent, you are using get_option to pull from the DB and in the options table the autoload flag is set. Under this circumstance, get_option will pull from memcache everytime. Also I only very rarely see you saving via update_option() which probably means when you save new options via admin-ajax the transients are not cleared.

Ah, AO does not use update_option, options are saved implicitly by form submitting, no admin-ajax (except for the clear cache link in the top menu bar).

Moreover as AO option saving does work on Redis (just tested again), the problem is unlikely to be a generic transients one?

What WordPress version are you on? I see WordPress 5.3.1 has changes specifically to fix issues with options saving, so this might be (somewhat) relevant?

Ah – I was planning to update to 5.3.1 (currently 5.3.0), later. I didn’t know it had fixes in it relating to saving options – thats interesting. I also noticed a slight tweak to the Memcached plugin (July) that our system doesn’t have yet.

I’ll update both today and come back to you.

Fingers crossed those updates will fix things ??

Sadly, updating didn’t fix the issue. If you are able to look into this I would be very grateful.

I should mention we have a large multisite install and settings for each site will be the same. Is there any way I can override settings via WP Config? This would solve this issue for us entirely.

hmm, multisite; in that case you’ll have to look into what AO 2.6 will bring. I’ll probably release in approx. 2 weeks time, but if you want you can download the beta here.

OK no problem – I will have a test of that when things quieten down later on tonight and I’ll come back to you.

Just to check, I assume any 500 style errors/kinks have been worked out already?

yep, the last big changes date from almost 2 months ago and the beta is already in use on a lot of sites and I consider it ready for release unless testers find any (non-minor) issues.

Hey Shane; don’t know if you found the time to test yet, but I just made this commit to beta which -if a filter is set to true, it’s off by default- will clear the option from the WP Object cache when in multisite, that should force the update to come through if the problem still exists.

Hi, thanks for the prompt. Yes I installed the beta that evening and it’s been running now for a couple of days. I have it network active with Enable site configuration set to on. I’m testing on three sites within the network at the moment. So far, so good! I’ve not noticed any issues at all ??

I’m going to leave settings as they are for now until we come back after Christmas – our company goes on a mini break after tomorrow untill Jan 2nd so I don’t want to make big site changes incase we inadvertently break something.

Thanks for the addition of the filter – that could prove to be very handy.

thanks for the feedback Shane, happy holidays! ??

Given no further feedback I’m assuming the BETA is still running smoothly, which is a relief given I’ll release (the day after) tomorrow! ??

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