-
v0.2.2 Stable
kw released this
2026-09-20 07:15:22 +00:00 | 2 commits to main since this release0.2.2 — saving a tab switched off the settings it never showed
An unticked checkbox sends nothing, so the settings form had to read
absence as "off". It read it that way for every setting in the group,
including the ones that have no control on any screen — so the first time
anybody pressed Save, three settings that are on by default were switched
off, with no message and no way to put them back.The request counters were one of them, which is why the dashboard said no
traffic had been measured on a site answering every request from the
cache. Clearing a page when it gets a comment was another. The hint that
tells a browser which image to load first was the third.Installing this switches them back on, says so in the activity list, and
the form can no longer do it.
Tested up to: 7.1
WC tested up to: 11.1.0Downloads
-
v0.2.1 Stable
2026-09-20 06:45:07 +00:00 | 2 commits to main since this release0.2.1 — the page cache was buffering every WP-CLI command
is_admin() is false under WP-CLI, so the guard list that keeps the cache
out of admin screens, AJAX, cron and REST let the command line straight
through: every wp command on a site running this plugin executed inside
the page cache's output buffer.Nothing could ever be stored from there — command output has no 200
status and no closing html tag, and either one refuses it. What it cost
was diagnosis: PHP holds buffered output until the command ends while an
error goes out at once, so a failure printed above the work that caused
it.
Tested up to: 7.1
WC tested up to: 11.1.0Downloads
-
v0.2.0 Stable
2026-09-20 06:11:55 +00:00 | 2 commits to main since this release0.2.0 — the assistant is where the question comes up
It was on its own page, which meant reading a setting, going somewhere
else, and describing the setting from memory. There is now a panel in the
corner of every screen this plugin owns. It carries the screen it was
opened on, so "is this right?" has something to refer to, and it offers a
couple of questions worth asking from where you are standing.It appears only when an assistant is configured, and never on the shared
family page.The family's menu carries an infinity sign now, because the family is
called Nolimit and a cog said nothing.
Tested up to: 7.1
WC tested up to: 11.1.0Downloads
-
v0.1.4 Stable
2026-09-20 06:01:39 +00:00 | 2 commits to main since this release0.1.4 — the dashboard now says why nothing was counted
The cache was answering every request on a live shop and the dashboard said
"No traffic measured yet". That sentence is what a quiet site says too, so
the screen could not be wrong, which is the actual defect.It now names the cause and measures each one rather than inferring it: the
configuration the engine really reads, a counter directory that is written
to instead of asked whether it is writable, and a drop-in that may be
loading a different copy of the plugin. Stored pages with no counted
requests is reported as the contradiction it is.Times are timestamps again. "Measured 2 dage ago" was half Danish and half
English, because WordPress answers "how long ago" in the site's language
and the words around it were ours.
Tested up to: 7.1
WC tested up to: 11.1.0Downloads
-
v0.1.3 Stable
2026-09-17 18:56:24 +00:00 | 2 commits to main since this releaseNolimit Cache 0.1.3
The setup guide no longer asks you to edit wp-config.php when there is
nothing to edit. A site where WP_CACHE is already switched on — by hand, or
by a cache plugin you used before — now passes that step even if the file is
read-only, which it should be on a live site.No change to caching behaviour.
https://gitea.nolimit.dk/kw/nolimit-cache-dist
Tested up to: 7.1
WC tested up to: 11.1.0Downloads
-
v0.1.2 Stable
2026-09-17 13:26:29 +00:00 | 2 commits to main since this releaseNolimit Cache 0.1.2
Fixes an updates screen that offered Nolimit Cache a version belonging to
another plugin. WordPress gives every plugin updating from the same host one
shared list, and a plugin that writes into its neighbours' rows can put its
own download behind their Update button. Nolimit Cache now refuses any
update for itself that does not come from its own release feed, and repairs
a list that was already wrong before this version was installed.Nothing else changes. If your updates screen has been offering Nolimit Cache
a version it does not have, this release clears it.https://gitea.nolimit.dk/kw/nolimit-cache-dist
Tested up to: 7.1
WC tested up to: 11.1.0Downloads
-
v0.1.1 Stable
2026-09-17 12:15:16 +00:00 | 2 commits to main since this releaseNolimit Cache 0.1.1
Hardening for a fault that shows up only when several of these plugins are
installed together. They all fetch updates from the same host, WordPress
gives them one shared hook, and a plugin that answers on behalf of its
neighbours can offer its own zip as their update. This release makes Nolimit
Cache answer last, so nothing else can overwrite what it reports about
itself.If your updates screen has offered Nolimit Cache a version it does not have,
install this one and the entry corrects itself.https://gitea.nolimit.dk/kw/nolimit-cache-dist
Tested up to: 7.1
WC tested up to: 11.1.0Downloads
-
v0.1.0 Stable
2026-09-17 11:50:40 +00:00 | 2 commits to main since this releaseNolimit Cache 0.1.0
Full-page caching for WordPress and WooCommerce that tells you what it is
doing. Every page it declines to cache says why, in one word you can read off
the response header, and the hit rate on the dashboard is counted rather than
sampled.It knows about a shop: a page built for somebody with a basket is never
stored, the checkout and account pages are excluded by their real addresses
rather than by guessing the English ones, and a stock or price change clears
the product page it affects.First release. https://gitea.nolimit.dk/kw/nolimit-cache-dist
Tested up to: 7.1
WC tested up to: 11.1.0Downloads