Linux 软件免费装
Banner图

ABCode Improved Caching for 20i StackCache

开发者 ashbrentnall
更新时间 2026年8月19日 02:01
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

cache performance cache purge stackcache 20i

下载

1.0.0

详情介绍:

This is an add-on for 20i StackCache, the cache plugin on 20i's Managed WordPress and WordPress Optimised hosting. It fills a specific gap in how StackCache clears its cache. When you publish or edit a post, StackCache purges only that post's own URL. Every other page that lists the post (your homepage, its category and tag archives, custom taxonomy archives, the post-type archive, the blog page and the main feed) keeps serving the old, cached version until its cache naturally expires. So a new or updated post can be missing, or shown with stale content, on exactly the pages your visitors browse to find it. This plugin closes that gap. What it does Safe by design Who it is for Anyone whose WordPress site is hosted on 20i (or a 20i reseller) with StackCache enabled, and who wants edits to show up straight away across their whole site instead of lingering behind the cache.

安装:

  1. Install and activate the plugin through Plugins → Add New, or upload the plugin folder to /wp-content/plugins/.
  2. That's it. As long as 20i StackCache is active, the plugin starts closing the hierarchy-purge gap immediately, and there is nothing to configure.
  3. Optionally install ABCode Cache Warmer so purged pages are rebuilt instantly rather than on the next visit.

屏幕截图:

  • The plugin tells you when StackCache is missing rather than sitting there doing nothing.

常见问题:

Do I need 20i StackCache for this to work?

Yes. This is an add-on for StackCache specifically. Without it, the plugin does nothing and shows a notice telling you so. StackCache ships with 20i's Managed WordPress and WordPress Optimised hosting.

Do I need the cache warmer too?

No. The purge on its own fixes the staleness: the next visitor to each listing page gets fresh content. The warmer is optional: with it, those pages are rebuilt right away so nobody has to be the first to wait.

What exactly gets purged when I edit a post?

The homepage, the post's public taxonomy archives (categories, tags, custom taxonomies), its post-type archive, any parent pages, the blog page if you use a static front page, and the main feed. The post's own URL is handled by StackCache; this plugin only adds it when StackCache would not (an unsupported custom post type with StackCache's custom-post-type purging turned off), so nothing is purged twice.

Will it purge pages on other sites, or anything off my domain?

No. Every URL is checked against your site's own host first. Anything off-domain is ignored.

Does purging on every edit slow down saving a post?

No. The purge is deferred to a short background task a few seconds after you save, so your editor request returns immediately. A burst of edits (such as a bulk action) folds into a single purge pass.

What is "Purge This Page"?

A control in the admin bar, on front-end views, that clears just the page you are looking at. It is protected by a capability check and a nonce. There is also a "Purge Everything" option for a full-site purge.

What happens if I deactivate StackCache, or the cache warmer?

Nothing breaks either way. The plugin checks StackCache is present before it does anything at all, so without it there are no purges, no scheduled tasks and no admin bar changes, just a notice telling you it is idle. The cache warmer is checked the same way: the plugin offers it the purged URLs, and if it is not installed that offer simply goes nowhere. Neither is bundled or modified; both stay entirely under your control.

Does it change how StackCache caches my site?

No. It does not touch StackCache's caching engine, settings or rules. It only issues additional purge requests through StackCache's own purge method for the listing pages StackCache leaves out, so your content stays consistent.

更新日志:

1.0.0