Home

Bext for WordPress

Welcome to the bext-wp wiki — the manual for the WordPress plugin that makes WordPress cooperate with the bext server (local or bext cloud) instead of fighting it.

Repository: https://github.com/webdesign29/bext-wp · License: GPL-2.0-or-later · PHP 7.4+ · WordPress 5.8+

What it does

bext-wp turns bext's edge cache from a blunt TTL into a precise, always-fresh cache, tames Action Scheduler, keeps personalized responses out of the anonymous cache, and gives operators a real dashboard — all configurable from Bext → Settings.

It's safe by default: every feature no-ops when the site isn't actually behind bext, fails open, and never edits wp-config.php or disables third-party plugins on its own.

The problem it solves

Running WordPress behind a reverse cache forces a bad trade-off:

	Long TTL	Short TTL
Speed	✅ fast	❌ first hit after each cycle = full PHP render (~4.4 s measured)
Freshness	❌ stale after edits	✅ fresh

bext-wp removes the trade-off: bext keeps a long TTL, and WordPress tells bext exactly which URLs changed the moment they change — fresh and fast. It also kills Action Scheduler's loopback admin-ajax self-calls (5–21 s) that tie up PHP-FPM workers.

Start here

• Installation — must-use (fleet) or normal plugin
• Configuration — Settings page + wp-config constants
• Connection Modes — Auto (local) vs Cloud (remote)
• Bext Cloud — remote endpoint + token setup

Reference

• Caching & Purging
• Action Scheduler & Cron
• SDK Bridge (email + jobs)
• Multisite (network settings + cross-site purge)
• Dashboard
• WP-CLI
• Hooks Reference
• Architecture
• Security

Operations

• Fleet Deployment — installing across many sites
• Auto-Updates — self-hosted plugin updates
• Troubleshooting
• FAQ
• Contributing & Releasing

---

Built and maintained with support from webdesign29 and Inklura.