ObjectNest Cache makes persistent object caching understandable and manageable inside WordPress. It connects WordPress to a Memcached server through the standard wp-content/object-cache.php drop-in and explains whether the PHP extension, server, and drop-in are working.

The plugin stays local-first. It does not create an account, send site data to a remote service, add frontend assets, or track visitors.

Features

Automatic discovery of common local Memcached endpoints.
Custom Memcached host and port configuration.
Connection test with actionable diagnostics.
Safe connect and disconnect controls.
Refuses to overwrite a foreign object-cache.php drop-in.
Live Memcached version, uptime, hit ratio, items, memory, connections, traffic, and evictions.
Optional disk object-cache fallback when Memcached is unavailable.
Explicit administrator-only cache flush action protected by a nonce.
Responsive, keyboard-friendly WordPress admin dashboard.
A compact WordPress Dashboard widget showing live hit ratio, memory, items, evictions, and uptime.

Requirements

WordPress 5.8 or newer.
PHP 7.4 or newer.
For Memcached: the PECL memcached extension and a reachable Memcached server.
The legacy PECL memcache extension is not the extension used by the Memcached backend.

Safety

ObjectNest never overwrites an object-cache.php file it does not own. Memcached should listen on a private interface or protected network; do not expose it to the public internet. Cache keys are salted per WordPress installation when the generated drop-in is created.

The Flush action affects the connected cache backend’s pool. Use it only when you understand whether that server is shared with other applications.