• My site was recently updated to WordPress 6.9. Since that update, I’m now getting the recommendation to use a Persistent Object Cache. The problem is, we do! My Networking Host did a huge bunch of updates last year, including making sure we were using Memcache. It’s been working fine, no errors or recommendations at all for months. Now, with this latest WordPress update, we’re getting this recommendation again.

    Does anyone know what about the latest WordPress update might have triggered this message to return?

    This has happened previously to us. We had a persistent object cache enabled, but then after one of the older WordPress updates (I no longer remember which one, this was several years ago), we started getting this recommendation. The latest server updates resolved this once and for all (or so I thought)

    Again, what about this update would have caused this message to reappear?

    Thanks in advance, if anyone knows the answer or has ideas how we can fix it. It’s just annoying, especially given we DO have a persistent object cache.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator bcworkz

    (@bcworkz)

    Your Memcache plugin may need to be updated. AFAIK, the plugin is required to signal to WP that it’s active, in addition to a slew of other integration. (signal via global $_wp_using_ext_object_cache) All the site health check routine does is check for this signal. It’s conceivable that Memcache is working fine, but it hasn’t properly signaled to WP that it’s there.

    Thread Starter aprildmoore

    (@aprildmoore)

    @bcworkz — thanks! We’ll look into that. Sounds like a very likely cause.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.