Caching and page speedPro
Inspect and flush Docket Cache from your AI client
Docket Cache stores WordPress's object cache as plain PHP files that OPcache keeps in memory, and GoBuildWP works with that model: it detects the plugin, reports whether the object-cache drop-in is live, flushes through wp_cache_flush(), and reads or writes options under docket_cache and docket-cache by name. Paths and the kill switch are constants, so those remain a wp-config.php job.
docket_cache- Layer
- object
- Declared purge scopes
all- Shared keys
- None
- Detected by
- plugin folder docket-cache
Installed class, method or listener checks and per-layer results determine whether a purge ran. Neither a declaration nor a returned ran flag proves public freshness.
- Edition
- Pro
- Abilities
- 16
- Requires
- WordPress 6.9+, PHP 8.0+
Before changing cache settings, inspect captured drivers and not_captured. After reverting, inspect restored, deleted, not_restored, verified and purged_layers. Use a separate cache-purge result when you need details for each layer. Storage verification checks captured values; it does not establish functional recovery or public freshness. Revert may overwrite later settings, and vendor configuration regeneration or a re-save can still be required.
Check each measurement run’s fetched_via before treating it as public-path evidence. cache-verify-in-browser supplies checks and does not operate a browser. Automatic purge coalesces targets within the request and runs on shutdown; it is not necessarily one immediate flush per call. Verify generated files, object/page/edge caches and actual visitor behavior separately.
Data model
Objects as PHP files, served by OPcache
Instead of a network service such as Redis, Docket writes each cached object to a PHP file and lets OPcache hold the compiled result. By default those files sit in wp-content/cache/docket-cache, set by DOCKET_CACHE_PATH, with separate data under wp-content/docket-cache-data, set by DOCKET_CACHE_DATA_PATH. Beyond the object cache it offers Advanced Post Cache, precaching, a menu cache, a translation (.mo) cache and an OPcache viewer.
Behaviour is governed largely by constants in wp-config.php, DOCKET_CACHE_DISABLED among them, and GoBuildWP never edits that file. The database side is a set of options whose names start with docket_cache or docket-cache; GoBuildWP's generic driver lists them and writes one exact name per key.
check-setup recognises Docket as the object-cache backend through its DOCKET_CACHE_VERSION constant, and only when WordPress reports an external object cache in use. That makes it the quickest way to tell an active plugin from a drop-in that is actually answering.
Option name prefixes
docket_cachedocket-cache
Object-cache accelerator with no page-cache settings to map. Its options are readable and writable by name.
Abilities
The cache abilities on a Docket site
| Ability | What it does here | Undo and limits |
|---|---|---|
cache-check-setup | Lists docket_cache as an object layer from the docket-cache folder and, with the drop-in loaded, reports object_cache.backend as docket. | An active plugin with object_cache.active false means Docket is installed but its drop-in is not in use. |
cache-purge | Calls wp_cache_flush() whatever scope is requested, and says in the layer result when a targeted request was widened. | Docket's narrower flushes (menu cache, .mo cache, precache, transients, advanced post cache) are WP-CLI subcommands GoBuildWP does not run. |
cache-warmcache-measure-page | After a flush, warming requests pages so the object files are written again, and repeated measurements show how long those rebuilds take. | Object caches set no hit header, so the HIT or MISS in measure-page belongs to a page cache or edge if there is one. |
cache-get-settingscache-set-native | List options under the two prefixes and change a single one after reading it back, with confirm=true. | Constants such as DOCKET_CACHE_PATH are not rows and are neither shown nor changeable. |
cache-set-settingscache-apply-presetcache-list-presets | Treat every canonical key as unsupported: an object cache has no page, CSS or image settings to tune. | Nothing here is risk-tiered. |
cache-list-actionscache-run-action | Offer nothing for Docket. Garbage collection exists as wp cache run:gc on the command line only. | No action means no action to refuse either. |
cache-begin-experimentcache-revert-experimentrollback-changecache-verify-in-browser | Snapshots and single-write undo cover the docket_cache and docket-cache rows; the browser checks are there for whatever page cache or optimiser sits in front. | Cached object files on disk are never part of a snapshot; a revert restores options and flushes, nothing more. |
Reference: /docs/reference/cache
Shared cache module; do not add this count across drivers. Edition and effect labels describe the source catalogue. The installed schema, dependency versions, licence, WordPress capability, safety profile and per-ability policy determine availability; labels alone do not prove confirmation or recovery.
Limits
Where Docket stays out of reach
- Paths, the DOCKET_CACHE_DISABLED switch and other constants live in wp-config.php, which no cache ability edits.
- Every purge of this layer is a full flush, and GoBuildWP coalesces automatic purge targets within a request and flushes at shutdown; the wppilot_cache_auto_purge option or filter turns that off.
- Granular flushes and drop-in management (wp cache dropin:enable, disable and update) are WP-CLI commands with no ability equivalent.
- Row writes are undoable with rollback-change; a flush is not. An emptied cache is rebuilt from the database, which costs rebuild time and extra database load while it refills, so flush a busy site at a quiet hour.
Other plugins
Docket with page caches and other object caches
- Docket's FAQ says to pair it with a page cache but not with another object cache, and to turn LiteSpeed Cache's Object Cache off when both are installed.
- For a busy WooCommerce store, or a VPS that already runs Redis, the vendor points to Redis instead of Docket.
Worked example
Rule Docket out when a deleted menu item keeps appearing
Expected outcome to verify on the installed stack; this sequence has not been recorded as a runtime test.
The call requests flushes from the supported object and page layers, then fetches the homepage. Inspect per-layer results and the rendered menu before reporting a rebuild. If the deleted item remains, check menu data and remaining delivery layers. Docket's own wp cache flush:menucache is the narrower shell equivalent.
Inspect actual menu data or origin HTML after per-layer purge results, then check external CDN, host and browser layers. Homepage warm does not prove origin rebuild. Expect temporary database or CPU rebuild load; automatic purges batch within the request.
The menu still shows a page I deleted. Could Docket Cache be holding on to it?
wppilot/cache-check-setupReadobject_cache.backend docket confirms the drop-in is answering; any page cache is listed as its own layer.
wppilot/cache-purgeWriteScope all: wp_cache_flush() for Docket and each page cache's full purge, reported layer by layer.
wppilot/cache-warmWriteRequests the home page so WordPress builds it again from the database; a response alone does not prove every cache layer served fresh output.
A suggested sequence from the ability reference, not a recorded run.
Questions
Docket Cache questions
Does GoBuildWP clear Docket's OPcache entries too?
GoBuildWP calls wp_cache_flush() and nothing else. How Docket handles its files and OPcache in response is Docket's own flush logic.
Can the agent turn Docket Cache off if the site breaks?
Not through the cache abilities. The vendor's switches are the DOCKET_CACHE_DISABLED constant and wp cache dropin:disable, both done by someone with file or shell access.
Where does Docket keep its cache files?
In wp-content/cache/docket-cache by default, movable with DOCKET_CACHE_PATH, per Docket's constants documentation.
Is Docket Cache a page cache?
No. It caches objects, which is why GoBuildWP classes it as an object layer and why presets have nothing to apply to it.
Docket Cache stores persistent objects as PHP code and uses OPcache acceleration. It targets cached application data. Before changing it, distinguish the object-cache drop-in from a page cache or CDN, inspect its own OPcache status and confirm that another object-cache provider is not active. A saved cache setting does not establish a faster database query or a healthy OPcache configuration. Docket Cache documentation
Where these facts come from
GoBuildWP behaviour is taken from the plugin source and the ability reference; third-party details from the vendor documentation below, checked by the GoBuildWP team.
Docket Cache is a separate product; no partnership or endorsement is implied.