Collaborative block editing.
Without HTTP polling.
WordPress 7.0 ships real-time collaborative editing in the block editor, built on Yjs. The default transport is HTTP polling. WordSocket registers as a WebSocket sync provider, replacing polling with a persistent low-latency connection the moment you connect.
What WordPress 7.0 ships
WordPress 7.0 introduces a collaborative block editor powered by the Yjs CRDT library. Multiple authors can edit the same post simultaneously and changes merge automatically without conflicts.
Out of the box, WordPress synchronises editor state over HTTP: the browser polls a REST endpoint on a short interval to exchange Yjs document updates. It works, but adds latency proportional to the poll interval and generates constant background traffic even when no one is typing.
What WordSocket adds
WordPress 7.0 exposes a sync.providers filter that lets
plugins register an alternative transport. WordSocket hooks into this
filter and registers itself as a WebSocket-based Yjs sync provider.
Yjs document updates flow as binary WebSocket frames over the same connection already open for realtime events. No second connection, no extra configuration. The switch happens automatically when you connect your site to WPSignal.
<Setup />
Running in under a minute
No server to configure. No Yjs infrastructure to manage.
-
1. Install WordSocket
Install from the WordPress plugin directory or via WP CLI. Requires WordPress 7.0+ for collaborative editing.
-
2. Connect to WPSignal
Go to WP Admin > WordSocket > Connection and click Connect. Your site registers automatically and the Yjs provider is enabled by default.
-
3. Open the block editor
Open any post with a second user. WordPress switches to the WebSocket transport automatically. No configuration required.
Common questions
Does this require WordPress 7.0?
Yes. The Yjs sync provider integration depends on @wordpress/sync, which ships in WordPress 7.0. The plugin detects the version and skips provider registration on older installs, falling back to standard WordPress behaviour.
Does it use a separate WebSocket connection?
No. Yjs document updates are relayed over the same persistent WebSocket connection already open for realtime events. There is no second connection.
What happens when WebSocket is unavailable?
The provider detects the SSE fallback and emits a "disconnected" status. WordPress surfaces its standard "not synced" indicator in the block editor toolbar. You can also disable the provider entirely from WordSocket > Settings > Connection to restore default WordPress HTTP polling.
Are Yjs document updates encrypted?
Yjs updates are relayed as binary frames and are not covered by the AES-256-GCM event encryption, which applies to JSON event payloads only. The relay forwards binary diffs without reading or storing document content.
Can I disable collaborative editing without deactivating the plugin?
Yes. WordSocket > Settings > Connection has a toggle to disable the Yjs provider and restore WordPress HTTP polling for all editors.
WordPress 7.0 is here
Switch from polling today
Free during beta. Install WordSocket, connect to WPSignal, and your block editor uses WebSocket sync automatically.