yes @optimizingmatters I also have Redis Object Cache plugin.
But since I remove and install again my issue is gone, so I can’t reproduce now…
But since I remove and install again my issue is gone, so I can’t reproduce now…
the problem, based on what we were able to puzzle together, is with a stale version of the “alloptions” object in the external object cache (due to a wordpress core bug), which causes AO to “see” the wrong value for autoptimize_version from that stale alloptions object and hence going through the upgrade-process time and time again until the stale alloptions gets refreshed.
removing & reinstalling removes and re-adds the autoptimize options, which is another way to clear the alloptions cache I guess 😉
there’s more detailed info in this thread; https://wordpress.org/support/topic/many-cachebuster-requests/page/2/#post-9832940
Thread Starter
luito
(@luito)
Hi Frank
Yes actually i working with memcache,
thank you for the version but still have problems with object cache module and when I use disk method for object cache, this working fine.
The new version still have the problem.
taking a step back first; can you check if you have those pesky “cachebuster”-requests in your access log (both before and after the update to the new version)?
Thread Starter
luito
(@luito)
I dont have requests like that.
ok, the fix in the new version _only_ addresses stale options in external object cache leading to continuous “cachebuster”-requests (of which I had several reports). you seem to be encountering a different problem, albeit also related to an external object cache. can you purge memcached and restart the daemon?
Just released 2.3.2.
@luito did you try the things I asked earlier in this thread?
Thread Starter
luito
(@luito)
Hi frank
Plugin reinstaled, cache cleaned and still I have the problem.
Just when i use memcache for object cache.
Working to find the problem.
Plugin reinstaled
2.3.2 or 2.2.2? because it would be interesting to know if 2.2.2 still works for you now.
Well, it would be interesting to test with 2.2.2 to see if this somehow related to something in the code (I wouldn’t know what, but still)?
Thread Starter
luito
(@luito)
Hi Frank
2.2.2 tested, problem persist.
W3 Total cache is the problem maybe im testing all modules.
2.2.2 tested, problem persist.
well, I’m relieved to be honest, that means it indeed is not a regression of AO 2.3 and it was a coincidence that you encountered it after upgrading.
W3 Total cache is the problem maybe im testing all modules.
maybe disable memcached in W3TC and install an alternative plugin to do object caching in memcached instead? that way you can confirm is the problem is memcached or W3TC?
