FAQ

FAQ

Do I need bext to use this plugin? Yes — it's an integration for sites served by bext. Without bext it stays dormant (no-ops, fails open), so it's harmless if left installed.

Is it safe to leave installed if I move off bext? Yes. In Auto mode it detects bext per request and no-ops otherwise. The sticky detection flag is cleared on deactivation/uninstall. Set Mode → Off to disable explicitly.

Does it replace WP Rocket / W3 Total Cache / a page-cache plugin? bext is the edge cache, so a separate WordPress page-cache layer is usually redundant. The plugin doesn't disable them for you; you can if you want.

Will it cache pages for logged-in users / carts? No. Logged-in, cart, comment-author, and preview requests are marked private, no-store, so bext keeps them out of the anonymous cache.

Why is wp bext purge --url=… not working? Use the positional form: wp bext purge /path/. --url and --path are WP-CLI global flags.

Does it work on multisite? Yes. Options are per-blog; a subdirectory-multisite full purge is scoped to the blog's path (not the whole network). A network-admin aggregate view is on the roadmap.

Does it work on subdirectory installs (site at /blog/)? Yes. Home, feeds, sitemaps and the REST collection are derived from WordPress + the install base path.

Do I need to open a port or relax open_basedir? No. Everything uses the bext main listener on 127.0.0.1:80 (Auto) or the configured HTTPS endpoint (Cloud) — no extra port, no file-system reads.

What PHP versions are supported? PHP 7.4+ (CI tests 7.4 / 8.1 / 8.3).

How do I purge from my own code? Use the admin bar, wp bext purge, the dashboard button, or the bext/purge_urls_for_post filter to shape automatic purges. A programmatic purge API may be added — open an issue if you need one.

Is it free / open source? Yes — GPL-2.0-or-later. Contributions welcome (see Contributing & Releasing).