Compatibility, stated plainly.
Support matrix
Versions and couplings.
| Surface | Supported | Status | Notes |
|---|---|---|---|
| WordPress core | 6.4 and newer (6.4.3 · 6.5.2 · 6.6 verified) | Supported | Older majors pair, but new connector features land on supported versions first. |
| PHP | 8.1 · 8.2 · 8.3 | Supported | The console flags sites still on EOL PHP as needing attention. |
| WooCommerce | Current release line | Pro and above | Read-only cross-store analytics: revenue, orders, products. Stores are auto-flagged so commands can exclude them. |
| Common plugins | WooCommerce, Yoast SEO, Elementor, Contact Form 7, WP Rocket, Advanced Custom Fields | Coexists | The connector manages these like any plugin — update it, activate or deactivate it, or exclude it from a bulk run. |
| WordPress.com sites | — | Out of scope | Plugin installation is restricted there; the connector can’t be installed. |
Restrictive hosts
When the host gets in the way.
Some managed hosts and security layers block the workspace’s signed requests before they reach the connector. The connector detects this at pairing and switches strategy automatically — you see the mode it chose on the site row.
Reverse-poll fallback
AutomaticIf inbound requests to the site are blocked, the connector stops waiting to be called and instead checks in with your workspace on a short interval, picking up pending commands and delivering heartbeats itself. Operations run the same; they can arrive a poll-cycle later. The site row shows reverse-poll instead of direct so you always know the mode.
Full outbound blocks
IncompatibleA host that blocks all outbound HTTPS from the site leaves the connector no channel in either direction — reverse-poll can’t help. Pairing fails with a plain reason instead of hanging, and the fix is on the host: allowlist the workspace endpoint, then pair again.
The install details live in the docs.
Pairing, reverse-poll, unpairing, and the per-host notes — all in the documentation index.