| 开发者 | |
|---|---|
| 更新时间 | 2026年9月12日 01:09 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
advanced-cache.php drop-in serves the final response before
WordPress or Composer boots. Logged-in, personalized, query-string, private,
non-HTML, and otherwise unsafe responses bypass the cache.
The plugin makes no external requests and collects no telemetry.
Version 1 supports single-site WordPress installations only. It does not edit
cached HTML, optimize HTML/CSS/JavaScript, cache media, warm pages, or use a
remote cache service.
basil directory to /wp-content/plugins/, or install the ZIP
from the Plugins screen.wp-config.php or install a drop-in.
The guided setup asks WordPress for filesystem access. When safe, it creates
cache/basil/ under the configured uploads directory, installs Basil's owned
advanced-cache.php in the configured content directory, and adds a marked
WP_CACHE block near the end of wp-config.php. It leaves an existing
WP_CACHE definition and every foreign drop-in unchanged, and explains when
manual action is necessary.
If another cache plugin leaves Basil's markers stale or incomplete, the
dashboard offers a protected repair action. It removes only exact Basil blocks
and marker comments while preserving other declarations and plugin settings.Basil captures completed templates through WordPress's native template enhancement buffer instead of opening its own long-lived output buffer. Sites that opt out of this buffer for streaming, or serve pages outside the normal template lifecycle, continue to work but do not generate cache entries.
No. Basil defaults to bypassing every request. Page caching requires guided setup and at least one enabled cache rule.
No. Basil bypasses requests that contain authentication, session, cart, or other known personalization signals.
No. Version 1 uses the local filesystem and makes no runtime external requests.
Only the guided setup can add Basil's marked WP_CACHE block and owned
advanced-cache.php drop-in. Runtime cache entries stay below
cache/basil/ under the configured uploads base. Basil verifies exact ownership
markers before removing any of these artifacts.
Basil reports the likely conflict and does not deactivate the other plugin or
overwrite its drop-in. An object-cache.php drop-in is not treated as a
page-cache conflict.
Basil reports that WP_CACHE needs repair and offers a protected dashboard
button. The repair removes only canonical Basil blocks and exact Basil marker
comments. Other WP_CACHE declarations, plugin settings, and unfamiliar
configuration remain unchanged.
Deactivation preserves rules but clears cached pages, scheduled cleanup, and only Basil-owned runtime/configuration artifacts. Uninstall also removes Basil's stored rules and private options. Foreign files and configuration are left untouched.
No. Version 1 detects multisite and keeps page caching disabled.
No. Editable final HTML is intentionally deferred. Manual changes to cache entries are unsupported and may make an entry fail validation and bypass.
filter_input().