Brightery Cache King
| 开发者 | brighterycom |
|---|---|
| 更新时间 | 2026年8月25日 01:05 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Static HTML cache for public pages, posts, archives, products, and public custom post types.
- Direct static delivery on compatible Apache and LiteSpeed servers.
- Early
advanced-cache.phpdelivery when direct web-server delivery is unavailable. - Generated Nginx configuration guidance for direct static delivery.
- Manual homepage builder and background full-site cache builder.
- Automatic cache invalidation after content and public site structure changes.
- Gzip precompression, ETag, Last-Modified, HEAD, and conditional-request support.
- Separate cache directories per host.
- Integration health checks and repair controls.
安装:
- In WordPress, go to Plugins > Add New Plugin > Upload Plugin.
- Upload
brightery-cache-king.zip. - Activate Brightery Cache King.
- Open Cache King from the WordPress admin menu.
- Review the integration check and use Repair installation if a writable-file step needs to be retried.
- Select Build homepage now or Build all static pages.
- Test the site in a logged-out or private browser window.
WP_CACHE, install its own advanced-cache.php drop-in, create its cache directory, and add marked Apache or LiteSpeed rules. If a protected file is not writable, the dashboard explains which manual step is required.
For Nginx, copy the generated directives into the existing site configuration, test the configuration, and reload Nginx.常见问题:
Does Cache King cache WordPress Admin or logged-in pages?
No. Administrative, authenticated, preview, background, and API requests are bypassed.
Does it cache WooCommerce carts or customer accounts?
No. Cart, checkout, account paths, WooCommerce session cookies, and private responses are excluded. Public product and product-category pages can be cached.
Does it require Redis, Memcached, a CDN, or an external API?
No. It uses local static files and standard WordPress and PHP functionality.
Is it literally zero-resource caching?
No HTTP response can use zero resources. On compatible Apache or LiteSpeed configurations, a cache hit can be served as a static file without starting PHP or WordPress. On Nginx, the generated server rule is required for the same direct-delivery behavior. Without a direct rule, the early drop-in starts minimal PHP and exits before normal WordPress loading.
Why should I test while logged out?
Logged-in frontend visits are intentionally bypassed. Use a private browser window or a separate logged-out browser to verify public cache behavior.
What happens when content changes?
When automatic purge is enabled, relevant content, comment, taxonomy, menu, theme, plugin, update, or public-setting changes clear the public cache. The homepage is queued for rebuilding, and other pages are rebuilt on their next anonymous visit or when you run the full-site builder.
Can I run another full-page cache plugin at the same time?
No. Two full-page caching systems may compete for advanced-cache.php, rewrite rules, and cache headers. Cache King does not overwrite a drop-in owned by another plugin and reports the conflict in its dashboard.
What does Cache King Pro add?
Cache King Pro adds scheduled full-site cache warming. The Free edition already includes manual homepage and full-site building.
What happens when I deactivate or delete the plugin?
Deactivation removes Cache King's generated integration rules, drop-in, and cache files while retaining settings. Deleting the plugin through WordPress also removes its saved settings.
更新日志:
- Replaced the plugin-managed response output buffer with the WordPress 6.9 template enhancement output buffer.
- Removed the unclosed plugin-managed response buffer lifecycle reported during WordPress.org plugin review.
- Replaced the direct file-handle implementations with compatible cache-file responses.
- Removed manual translation loading; WordPress.org now loads translations automatically.
- Renamed plugin code, hooks, nonces, handles, and generated drop-in identifiers with the unique
brightery_cache_kingprefix. - Corrected the WordPress.org plugin-header metadata.
- Updated filesystem access, request handling, and translation context for Plugin Check compliance.
- Fixed direct Apache homepage caching when plain permalinks are enabled.
- Added signed, cookie-free homepage generation.
- Added a manual background full-site builder for published public content.
- Added homepage cache health and build progress to the dashboard.
- Added generated, site-specific Nginx
try_filesguidance. - Added Apache RewriteBase, HEAD support, warm-request bypass, and Apache 2.4 END handling.
- Preserved login, session, ecommerce, API, preview, and private-response safety bypasses.
- Initial static HTML page-cache release.