Skip to content
Traslatability traslatability

NimbleCache Changelog

Serve your pages before WordPress even loads — and never touch a setting to do it.

NimbleCache

Release history

Every version, what changed, and when it shipped.

  1. 1.1.9
    • Saving now says what was saved. Every screen answered with the same word — “Saved.” — which tells you the one thing you already knew, that you pressed the button. Each screen names what it kept.
    • The confirmation message has no close button and more room at both ends: it leaves on its own after four seconds, and clicking anywhere on it dismisses it.
  2. 1.1.8
    • Confirmation and error messages are easier to see: rounder, and coloured by what they are saying — green for saved, red for something rejected, amber for something to look at — each with a mark of its own.
    • A licence message now looks like one. Activating a key answered in an unmarked grey box, whatever it said; it carries the right colour and a mark like every other message on the screen.
    • A licence key that could not be a key is refused on the spot, without a request to the licence server and without reloading the screen. An empty box used to mean a wait, and on an offline site it meant being told the licence server could not be reached.
    • A key pasted out of an email in lower case, or with the dashes lost, is put right rather than reported as wrong.
  3. 1.1.7
    • Confirmation messages line up properly and sit on rounder corners: they were top-aligned with the text nudged down two pixels to meet the icon, which on a one-line message read as a misalignment because it was one.
  4. 1.1.6
    • Confirmations are easier to see. The message after a save is bordered in the colour of what it is telling you, sized to the words rather than stretched to a fixed card, and it now says what was saved rather than just "Saved".
    • It stays for four seconds instead of three — long enough to read a sentence — and hovering it holds it open.
  5. 1.1.5
    • Tab changes are instant. The plugin's other screens are fetched quietly in the background while you read the first one, so by the time you click a tab there is nothing left to wait for — tens of milliseconds instead of a second and a half.
    • One at a time, never in parallel, started only once the screen you are on is ready and the browser says it is idle, stopped the moment you navigate, and skipped entirely on a metered connection.
  6. 1.1.4
    • An admin that never reloads. Every screen arrives without a page load and every save happens where you are standing — and the screen you are heading for is usually already fetched, because moving a pointer to a menu item takes long enough to fetch it.
    • Saved, and told so where you are looking. A save answers in a small message in the top-right corner that clears itself after a few seconds, instead of reloading the page and putting a notice above the header.
    • It is an enhancement, not a dependency: if a fetch fails or scripting is off, links navigate and forms submit exactly as they always did, and the server side is unchanged.
  7. 1.1.3
    • Notices redesigned: a quiet bordered card at 14px with the tone carried by a tinted icon, rather than a block of colour in coloured type.
    • The Rules screen back in two columns, split by what the question is: which pages on the left, the technical exceptions on the right.
    • Fixed three custom properties that were misspelt in the stylesheet.
  8. 1.1.2
    • The pages-cached figure is live again on any normal site. It is counted on the spot when the cache is small enough for that to cost nothing, and read from the last full measurement when it is not — so emptying the cache and then looking at the dashboard no longer reports nothing cached while pages plainly are.
  9. 1.1.1
    • Built for a very large site. Every job over the cache — counting it, weighing it, expiring old pages, trimming to a size ceiling — now streams one folder at a time instead of listing every file at once. A million cached pages cost the same memory as a hundred; before, that list alone was more than a shared host's whole memory limit.
    • The dashboard no longer walks the cache while you wait. It reads a remembered measurement, refreshed by cron where there is time. Emptying the cache used to count a million files just to tell you how many went.
    • A sitemap index is read a few children per run, from where the last run stopped. A shop with five hundred child sitemaps was five hundred requests to its own server inside one cron tick.
    • Notes redesigned — a white card with one coloured rule and text you can read, rather than a tinted block in tinted type.
    • The Rules screen reorganised: the two halves of the question stacked full width so neither is squeezed, and the technical exceptions grouped in a row of their own.
  10. 1.1.0
    • Choose which pages are cached. A new Rules screen answers it from both ends: cache everywhere, the front page only, shop and product pages, or exactly the post types, archives and individual pages you tick. Same control as every other Traslatability plugin.
    • A new Integrations screen naming what it found on your site — WooCommerce, Easy Digital Downloads, WPML, Polylang, TranslatePress — and exactly what it does about each. It reports rather than asks, because a basket page is not cacheable in a way anybody could have an opinion about.
    • Warms pages up from your sitemap. WordPress's own, Yoast's, Rank Math's or a plain sitemap.xml — the list your site already says matters, with noindex pages left out.
    • Decides its own pace. Reads the memory limit, the execution limit and the load average before any background work, halves its rate on a small host and stands down entirely while the server is busy. Shown on Diagnostics under "What this server can spare".
    • An optional ceiling on disk use, from 250 MB to 10 GB. Over it, the pages nobody has needed for longest are cleared first, a few at a time in the background.
    • Multi-currency shops now cache each currency separately rather than serving the first visitor's currency to everybody.
    • One name for one thing: the dashboard and the settings screen both call it warming pages up.
  11. 1.0.0
    • First release. Full-page caching that answers before WordPress loads: a cached page costs one file include, one hash and one file read, with no database connection and no plugins loaded.
    • Installs its own fast path — advanced-cache.php and WP_CACHE — and says exactly what to do by hand when wp-config.php is read-only.
    • Purges the page you changed and the pages that list it, not the whole cache.
    • WooCommerce and Easy Digital Downloads handled properly: baskets, checkouts and account pages never cached, stock and price changes purged the moment they happen.
    • Diagnostics that name the rule which stopped a page being cached, then fetch it twice to prove what the server really did.
    • Stampede protection, so a hundred visitors to an expiring page cause one rebuild rather than a hundred.
    • Compressed copies written once, conditional requests answered with 304, and tracking parameters stripped from the cache key.
    • No Redis, no WP-CLI, no SSH and no server modules required. Works on a single site or a multisite network.
    • Spanish and French included.

Get NimbleCache

One licence, every feature. Updates and support included.

See pricing