WPBridge Studio

WPBridge Studio

Check your site before purchasing

Studio supports authenticated WordPress REST operations. An installed plugin is usable through Studio only when its desired action has a compatible REST endpoint and the connected user has permission.

Supported and unverified workflows

Studio workflow boundaries
Workflow Current support
Posts and pages Core REST reads and changes, subject to native permissions and access mode.
Plugin-specific settings Requires a compatible REST route; dashboard-only actions are not guaranteed.
Theme files and WP-CLI No dedicated file editor or WP-CLI tool is included.
Paid direct-mode activation Pending; current purchases apply to the separate hosted service.

A practical pre-purchase check

  1. Confirm the site uses HTTPS and accepts authenticated REST requests.
  2. Choose direct WordPress mode or the separately hosted customer workspace.
  3. List the target REST routes and verify the user’s capabilities.
  4. Read a known draft and confirm its ID and title.
  5. For changes, test a disposable staging draft and read it back.

Successful status checks verify connectivity; they do not prove every plugin’s settings are remotely editable.

Can I use a CDN?

Public pages may use a CDN. The Studio OAuth and authenticated REST routes return private no-store headers. Configure the CDN to respect those headers and bypass caching for authentication and Studio REST endpoints. A firewall must also allow OAuth discovery and authorized requests.