All 33 NimbleCache answers

See every answer

Answer

The dashboard says caching is not running yet

Updated NimbleCache 1.7.0Tested with WordPress 7.1

Nothing is cached until both halves of the fast path are in place: wp-content/advanced-cache.php, and WP_CACHE in wp-config.php. The Fast Path list on the Dashboard says which one is missing, and the notice on the Plugins screen says why. Press Set up caching and the plugin puts both there. On a network, only a network administrator can.

If wp-content is not writable, the Dashboard names the folder: ask your host to let the web server write to it, or copy advanced-cache.php from the plugin's folder into wp-content yourself.

If it still says so, wp-config.php is probably read-only — on many hosts that is deliberate, and good practice rather than a fault. Add this yourself, immediately below the opening <?php:

define( 'WP_CACHE', true );

It must be near the top. Below the "stop editing" comment is too late.

Still stuck? Ask the developers who wrote it. We aim to reply within one business day.

NimbleCache

Serve your pages before the plugins load — and never touch a setting to do it.

From $19 a year · every feature · 30-day refund

Buy NimbleCacheSee the plugin

The NimbleCache dashboard in WordPress admin. A green notice reads The cache is on and pages are served before WordPress loads. Four cards show 11 pages cached (2 MB), an average build of 229 ms, a 12 hour page lifetime and preloading off. A Fast Path panel ticks off advanced-cache.php installed and current, WP_CACHE switched on in wp-config.php, the cache directory writable and compressed pages. An Exclusions panel lists what is never cached, and a Clearing Log lists recent full clears with the plugin that probably caused each.