basilcache.com<\/a><\/p>\n\nThe Basil dashboard reports setup, ownership, conflict, and cache-directory\nstate. If caching is unavailable, first review its contextual guidance and\nconfirm that WordPress can write wp-config.php<\/code>, wp-content\/<\/code>, and the cache\ndirectory through the configured filesystem method.<\/p>\n\nWhen requesting support, include the Basil and WordPress versions, PHP version,\nthe dashboard status text, and reproducible rule inputs. Do not publish cached\nHTML, cookies, authorization headers, filesystem credentials, or private site\ndata.<\/p>\n\n
Privacy<\/h3>\n\n
Basil does not send data to third parties or collect telemetry. Cached files\ncontain final anonymous HTML responses and private cache metadata on the local\nserver. Depending on the rendered page, that anonymous HTML may contain public\nsite content or visitor-independent output produced by other plugins. Site\nadministrators are responsible for configuring rules that exclude dynamic or\npersonalized pages. Administrators can purge these files from the Basil\ndashboard.<\/p>\n\n\n
\n- Upload the
basil<\/code> directory to \/wp-content\/plugins\/<\/code>, or install the ZIP\nfrom the Plugins screen.<\/li>\n- Activate Basil from the Plugins screen.<\/li>\n
- Open the Basil dashboard and follow the guided page-cache setup.<\/li>\n
- Add explicit cache rules. Requests that match no rule bypass the cache.<\/li>\n<\/ol>\n\n
Activation alone does not edit wp-config.php<\/code> or install a drop-in.<\/p>\n\nThe guided setup asks WordPress for filesystem access. When safe, it creates\n cache\/basil\/ under the configured uploads directory, installs Basil's owned\n advanced-cache.php in the configured content directory, and adds a marked\n WP_CACHE block near the end of wp-config.php<\/code>. It leaves an existing\n WP_CACHE definition and every foreign drop-in unchanged, and explains when\nmanual action is necessary.\nIf another cache plugin leaves Basil's markers stale or incomplete, the\ndashboard offers a protected repair action. It removes only exact Basil blocks\nand marker comments while preserving other declarations and plugin settings.<\/p>\n\n\n\nWhy does Basil require WordPress 6.9?<\/h3><\/dt>\nBasil captures completed templates through WordPress's native template\nenhancement buffer instead of opening its own long-lived output buffer. Sites\nthat opt out of this buffer for streaming, or serve pages outside the normal\ntemplate lifecycle, continue to work but do not generate cache entries.<\/p><\/dd>\n
Does Basil cache pages immediately after activation?<\/h3><\/dt>\nNo. Basil defaults to bypassing every request. Page caching requires guided\nsetup and at least one enabled cache rule.<\/p><\/dd>\n
Does Basil cache pages for logged-in visitors?<\/h3><\/dt>\nNo. Basil bypasses requests that contain authentication, session, cart, or\nother known personalization signals.<\/p><\/dd>\n
Does Basil use a remote service or send telemetry?<\/h3><\/dt>\nNo. Version 1 uses the local filesystem and makes no runtime external requests.<\/p><\/dd>\n
What files and configuration can Basil change?<\/h3><\/dt>\nOnly the guided setup can add Basil's marked WP_CACHE<\/code> block and owned\n advanced-cache.php drop-in. Runtime cache entries stay below\n cache\/basil\/ under the configured uploads base. Basil verifies exact ownership\nmarkers before removing any of these artifacts.<\/p><\/dd>\nWhat happens when another page-cache plugin is active?<\/h3><\/dt>\nBasil reports the likely conflict and does not deactivate the other plugin or\noverwrite its drop-in. An object-cache.php<\/code> drop-in is not treated as a\npage-cache conflict.<\/p><\/dd>\nWhat if another cache plugin changes Basil's wp-config.php markers?<\/h3><\/dt>\nBasil reports that WP_CACHE<\/code> needs repair and offers a protected dashboard\nbutton. The repair removes only canonical Basil blocks and exact Basil marker\ncomments. Other WP_CACHE<\/code> declarations, plugin settings, and unfamiliar\nconfiguration remain unchanged.<\/p><\/dd>\nWhat happens on deactivation or uninstall?<\/h3><\/dt>\nDeactivation preserves rules but clears cached pages, scheduled cleanup, and\nonly Basil-owned runtime\/configuration artifacts. Uninstall also removes\nBasil's stored rules and private options. Foreign files and configuration are\nleft untouched.<\/p><\/dd>\n
Is multisite supported?<\/h3><\/dt>\nNo. Version 1 detects multisite and keeps page caching disabled.<\/p><\/dd>\n
Can I edit generated cache files?<\/h3><\/dt>\nNo. Editable final HTML is intentionally deferred. Manual changes to cache\nentries are unsupported and may make an entry fail validation and bypass.<\/p><\/dd>\n\n<\/dl>\n\n\n
0.1.5<\/h4>\n\n\n- Require WordPress 6.9 and use its native finalized-template buffer for response capture; respect streaming opt-outs.<\/li>\n
- Store cache data under the configured uploads directory and honor relocated filesystem paths.<\/li>\n
- Move the Basil admin menu below Settings.<\/li>\n<\/ul>\n\n
0.1.4<\/h4>\n\n\n- Make Basil dashboard and rule-operation notices dismissible.<\/li>\n
- Remember configured-cache notice dismissal per administrator across reloads.<\/li>\n
- Preserve visibility of separate safety warnings and remove dismissal data on uninstall.<\/li>\n<\/ul>\n\n
0.1.3<\/h4>\n\n\n- Add one-click recovery for stale or incomplete Basil wp-config.php markers.<\/li>\n
- Preserve other cache plugins' declarations and configuration during repair.<\/li>\n
- Report damaged Basil marker state as \"Needs repair\" instead of unavailable.<\/li>\n<\/ul>\n\n
0.1.2<\/h4>\n\n\n- Add a one-click all-pages Lite quick start.<\/li>\n
- Add dashboard, website, contact, and toolbar shortcuts.<\/li>\n
- Move Basil higher in the administration menu and name its Dashboard submenu.<\/li>\n
- Make the configured-cache notice dismissible and add guarded directory indexes.<\/li>\n<\/ul>\n\n
0.1.1<\/h4>\n\n\n- Fix cache generation on FastCGI configurations where PHP does not expose request server fields through
filter_input()<\/code>.<\/li>\n- Show the configured WordPress timezone next to the scheduled cleanup time.<\/li>\n<\/ul>\n\n
0.1.0<\/h4>\n\n\n- Initial release of layered cache rules and local static HTML page caching.<\/li>\n<\/ul>","raw_excerpt":"Rule-driven static page caching with explicit, deterministic control over which pages may be cached.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/roh.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/363731","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/roh.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/roh.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/roh.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=363731"}],"author":[{"embeddable":true,"href":"https:\/\/roh.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/basilcache"}],"wp:attachment":[{"href":"https:\/\/roh.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=363731"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/roh.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=363731"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/roh.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=363731"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/roh.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=363731"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/roh.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=363731"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/roh.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=363731"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}