Title: WordSocket Author: wpsignal Published: mars 30, 2026 Last modified: avril 3, 2026 --- Search plugins ![](https://ps.w.org/wordsocket/assets/banner-772x250.png?rev=3495083) ![](https://ps.w.org/wordsocket/assets/icon-256x256.gif?rev=3495083) # WordSocket By [wpsignal](https://profiles.wordpress.org/wpsignal/) [Download](https://downloads.wordpress.org/plugin/wordsocket.0.13.2.zip) * [Details](https://tah.wordpress.org/plugins/wordsocket/#description) * [Reviews](https://tah.wordpress.org/plugins/wordsocket/#reviews) * [Installation](https://tah.wordpress.org/plugins/wordsocket/#installation) * [Development](https://tah.wordpress.org/plugins/wordsocket/#developers) [Support](https://wordpress.org/support/plugin/wordsocket/) ## Description WordSocket sends realtime events from your WordPress site to connected browsers. When content changes: a post is published, a comment is approved, an option is updated: the plugin pushes the event to subscribers instantly via WebSocket (with SSE fallback). On WordPress 7.0+, WordSocket also registers as a WebSocket-based Yjs sync provider for real-time collaborative editing in the block editor, replacing the default HTTP polling transport with a low-latency WebSocket connection. WPSignal is an independent service and is not affiliated with or endorsed by the WordPress project. **Features:** * One-click automatic connection via the WPSignal dashboard (no API key required) * Manual connection via API key for self-hosted or advanced setups * Disconnect button with inline confirmation, removes the site from the server immediately * WebSocket-first with automatic SSE fallback * Per-site JWT signing secrets: each site’s connection tokens are cryptographically isolated * AES-256-GCM encrypted event payloads: the WPSignal relay receives ciphertext only and never has access to plaintext message content * Real-time collaborative editing in the block editor (WordPress 7.0+, via Yjs sync provider) * Admin toggle to disable the collaboration provider and fall back to WordPress HTTP polling * Built-in triggers for post updates and custom post types * Custom trigger builder: map any WordPress action hook to a realtime event * Public JavaScript API (`window.WPS`) for themes and plugins to share the connection * Extensible connection token: `wpsignal_token_channels` and `wpsignal_token_channel_prefixes` filters let other plugins add channels and namespace permissions to the JWT without modifying core * Admin explorer page with live event log, publish form, and token inspector * Short-lived JWTs (5 min) with automatic refresh **How it works:** 1. Install the plugin and connect to the WPSignal service. 2. When content changes in WordPress, the plugin encrypts and publishes an HMAC-signed event to the WPSignal server. 3. The server pushes the ciphertext to all browsers subscribed to that channel. 4. The browser decrypts the payload and dispatches `wpsignal:*` DOM events. The relay never sees plaintext content. 5. On WordPress 7.0+, the block editor uses the same WebSocket connection for collaborative editing with no extra configuration. #### Third-Party Service This plugin connects to the **WPSignal service** at [api.wpsignal.io](https://api.wpsignal.io) for the following operations: * **Site registration**: when you connect in the admin (via the automatic one-click flow or by entering an API key manually), the plugin registers your site with the server and receives credentials. * **Event publishing**: when a trigger fires (e.g. a post is saved), the plugin sends an encrypted, HMAC-signed HTTP request to the server. * **Realtime connections**: logged-in users’ browsers connect to the server via WebSocket or SSE to receive events. * **Collaborative editing**: on WordPress 7.0+, Yjs document updates are relayed over the same WebSocket connection. Event payloads are AES-256-GCM encrypted before leaving WordPress. The WPSignal server relays ciphertext and never has access to plaintext message content. Data is delivered in realtime and is **not persisted** on the server. * [Terms of Service](https://wpsignal.io/terms) * [Privacy Policy](https://wpsignal.io/privacy) ### Building from source The JavaScript files distributed with this plugin (`build/client.js`, `build/settings. js`, `build/explorer.js`, `build/yjs-provider.js`) are compiled from TypeScript source using `@wordpress/scripts` (webpack). The full source code is publicly available: * Source repository: https://github.com/wpsignal/wordsocket To build locally: 1. Clone or download the repository. 2. Navigate to the `wp-plugin/` directory. 3. Run `npm install` to install dependencies. 4. Run `npm run build` to compile all scripts to `build/`. Source entry points: * `src/client.ts` compiles to `build/client.js` * `src/settings/index.tsx` compiles to `build/settings.js` * `src/explorer.ts` compiles to `build/explorer.js` * `src/yjs-provider-boot.ts` compiles to `build/yjs-provider.js` ## Screenshots * [[ * Settings page (Connection tab): Automatic connection mode with a « Connect with WPSignal » button, and a toggle to register WordSocket as the Yjs sync provider for real-time collaboration. * [[ * WPSignal dashboard authorization screen: one-click OAuth-style prompt to authorize a WordPress site and link it to your WPSignal account. * [[ * Settings page (connected): active connection confirmed with site key, Disconnect button, and real-time collaboration toggle enabled. * [[ * Settings page (Triggers tab): no-code trigger builder for Post Type and Option events, with channel and event name fields and a « Triggers saved » confirmation. * [[ * Explorer page (top): connection status panel showing server URL, site key, and live health check result, plus the Registered Triggers table listing all active hooks, priorities, and channels. * [[ * Explorer page (bottom): Live Event Log showing a live WebSocket connection and an incoming encrypted event, alongside the Publish Test Event form with channel, event name, and JSON data fields. ## Installation 1. Upload the `wordsocket` folder to `/wp-content/plugins/`, or install directly from the WordPress plugin directory. 2. Activate the plugin through the « Plugins » menu in WordPress. 3. Go to **WordSocket > Settings > Connection**. 4. Choose a connection method: 5. * **Automatic (recommended):** Click **Connect with WPSignal**. You will be redirected to the WPSignal dashboard to authorize the connection. No API key entry required. * **Manual:** Switch to the Manual tab, paste your API key, and click **Save Settings**. 6. The plugin registers with the server and saves credentials automatically. To create an account, visit [wpsignal.io](https://wpsignal.io). ## FAQ ### What is WPSignal? WPSignal is a realtime event delivery service for WordPress. It pushes events from your site to connected browsers the moment they happen, without polling. ### Do I need a wpsignal.io account? Yes. The plugin requires a WPSignal server to relay events. You can use the hosted service at wpsignal.io (free account available) or run your own server. ### What data is sent to the WPSignal server? During registration: your site URL and name. During normal operation: AES-256-GCM encrypted event payloads (the server never sees plaintext content). On WordPress 7.0+, Yjs document updates (binary diffs of block editor content) are also relayed. All data is delivered in realtime and is not stored on the server. See our [Privacy Policy](https://wpsignal.io/privacy) for full details. ### Are my event payloads private? Event payloads are encrypted with AES-256-GCM before leaving WordPress. The encryption key is derived from your WordPress salts and site key using HKDF-SHA256, and is never sent to the WPSignal server. This means the relay cannot read your message content. Note: all logged-in users on the same site share the same derived key. Per-user message privacy is out of scope for the current version. ### Can I use this with a self-hosted server? Yes. Enter your server URL in **WordSocket > Settings** instead of the default ` api.wpsignal.io`. ### Does this work for logged-out visitors? The built-in client script loads for logged-in users by default. You can enqueue the script for all visitors by adding `wpsignal` as a dependency to your own script. ### What happens if WebSocket is unavailable? The client falls back to SSE for receiving events. `window.WPS.subscribe()` and ` window.WPS.unsubscribe()` work on SSE connections: channel changes are tracked and applied immediately via a lightweight SSE reconnect (50 ms debounce). For collaborative editing, the plugin detects the fallback and emits a « not synced » status so WordPress can surface the appropriate indicator. You can also disable the collaboration provider entirely from **WordSocket > Settings > Connection** to restore WordPress HTTP polling for all editors. ### Does collaborative editing require WordPress 7.0? Yes. The Yjs sync provider integration requires WordPress 7.0 or later. The plugin detects the WordPress version and only registers the provider when `@wordpress/sync` is available. ## Reviews ![](https://secure.gravatar.com/avatar/3233cb79ca4a3a06619bf670bc308dfffb7ee61e685aa7011d84e66da9fd1f8c? s=60&d=retro&r=g) ### 󠀁[RTC no longer a performance concern](https://wordpress.org/support/topic/rtc-no-longer-a-performance-concern/)󠁿 [worldhouse](https://profiles.wordpress.org/worldhouse/) mars 30, 2026 After creating an account on wpsignal.io, activating the plugin, upgrading to WordPress 7, activating RTC (Settings > Writing) Real-time Collaboration worked beautifully with no performance knock to the user experience. [ Read all 1 review ](https://wordpress.org/support/plugin/wordsocket/reviews/) ## Contributors & Developers “WordSocket” is open source software. The following people have contributed to this plugin. Contributors * [ wpsignal ](https://profiles.wordpress.org/wpsignal/) [Translate “WordSocket” into your language.](https://translate.wordpress.org/projects/wp-plugins/wordsocket) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/wordsocket/), check out the [SVN repository](https://plugins.svn.wordpress.org/wordsocket/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/wordsocket/) by [RSS](https://plugins.trac.wordpress.org/log/wordsocket/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 0.13.1 * Updated screenshots #### 0.13.0 * Exclude BETA.md from plugin build #### 0.12.0 * feat: skeleton preloader for app.feat: disable automatic authentication for non- ssl.fix: disable encryption when on non-ssl. #### 0.9.0 * Fix: non-ssl default to manual authentication #### 0.8.0 * Improved: Connections UI. Reduced connections from 2 to 1 on connections page. * Fix: option key change for RTC enabled. #### 0.7.0 * New: Automatic connection flow. Admins can connect via the WPSignal dashboard with a single click, without entering an API key. Uses a CSRF-protected OAuth- style code exchange. * New: Disconnect button in the Connection tab. Removes the site from the WPSignal server and clears all local credentials, with inline confirmation before proceeding. * New: Per-site JWT signing secrets. Each site’s connection tokens are now signed with a unique secret, isolating sites cryptographically and eliminating cross- site token forgery risk. * Improved: Connection tab redesigned with Automatic and Manual sub-tabs to clearly separate the two connection methods. * Improved: Disconnect works correctly regardless of how the site was connected: API key authentication for manual connections, publish-secret authentication for automatic connections. #### 0.6.0 * New: Plugin renamed to « WordSocket » to comply with WordPress.org plugin directory guidelines. * Improved: Settings Connection tab revamped: server URL field removed, flow simplified to API Key entry and a single Connect action. * Improved: API key validated client-side before attempting connection. * Improved: Connection tab now surfaces WordPress real-time collaboration (RTC) availability and WP version compatibility, with clearer, more descriptive warnings when collaborative editing is unavailable. * Improved: PHP documentation blocks updated across all core classes for better tooling and doc parser support. * Developer: `.pot` language file added (`eventra-for-wpsignal.pot`). #### 0.5.1 * Fixed: WordPress 7.0 Beta 2 compatibility for the Yjs sync provider. Collection- level providers (e.g. collaborative notes) receive a null `objectId`; the provider now maps this to a shared `"collection"` channel suffix so all peers join the same channel. * Fixed: `ProviderCreatorOptions` type updated to accept `objectId: string | number | null`, matching the Beta 2 provider creator API. #### 0.5.0 * New: `wpsignal_token_channels` filter: plugins can append channels to the initial auto-subscribe list in the minted JWT. * New: `wpsignal_token_channel_prefixes` filter: plugins can add channel-prefix permissions to the JWT `allowed_channel_prefixes` claim, enabling server-enforced access to custom channel namespaces. * Improved: `window.WPS.subscribe()` and `window.WPS.unsubscribe()` now work on SSE connections. Channel changes are tracked in a persistent set and applied immediately via a debounced SSE reconnect, so plugins that call these methods do not need to know the current transport. * Developer: `forceSSE` config flag available for testing the SSE transport without browser tooling. #### 0.4.0 * New: AES-256-GCM encrypted event payloads. The WPSignal relay receives and forwards ciphertext only: plaintext message content never leaves WordPress. * New: Encryption key derived from WordPress salts and site key via HKDF-SHA256. Key is never transmitted to the WPSignal server. * New: `wpsignal_encryption_seed` filter for plugins and themes to supply custom key material. * New: `SubtleCrypto` decryption in the browser client: events are dispatched only after successful decryption. #### 0.3.0 * New: Real-time collaborative editing in the block editor (WordPress 7.0+) via Yjs WebSocket sync provider. * New: `publishBinary()` and `onBinaryMessage()` methods on `window.WPS` for binary WebSocket frames. * New: `transport` property on `window.WPS` exposes the current connection type(`' ws'`, `'sse'`, or `null`). * New: Admin toggle in Settings to enable or disable the real-time collaboration provider independently. * Improved: Collaboration provider emits `disconnected` status when WebSocket is unavailable, allowing WordPress to show its « not synced » indicator. #### 0.2.0 * New: Custom trigger builder: register triggers from the admin UI without code. * New: Settings page rebuilt as a React app with Connection and Triggers tabs. * New: Explorer (Kitchen Sink) admin page with 5 interactive panels. * New: Public JavaScript API (`window.WPS`): subscribe, publish, event listeners. * New: `WPS::trigger()` fluent builder and `WPS::publish()` facade methods. * New: Support for self-hosted servers (configurable server URL). * Improved: OOP architecture with PSR-4 autoloading under the `WPSignal` namespace. * Improved: TypeScript source with `@wordpress/scripts` build pipeline. #### 0.1.0 * Initial release. ## Meta * Version **0.13.2** * Last updated **4 heures ago** * Active installations **Fewer than 10** * WordPress version ** 6.2 or higher ** * Tested up to **7.0** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/wordsocket/) * Tags * [collaboration](https://tah.wordpress.org/plugins/tags/collaboration/)[events](https://tah.wordpress.org/plugins/tags/events/) [push](https://tah.wordpress.org/plugins/tags/push/)[realtime](https://tah.wordpress.org/plugins/tags/realtime/) [Websocket](https://tah.wordpress.org/plugins/tags/websocket/) * [Advanced View](https://tah.wordpress.org/plugins/wordsocket/advanced/) ## Ratings 5 out of 5 stars. * [ 1 5-star review ](https://wordpress.org/support/plugin/wordsocket/reviews/?filter=5) * [ 0 4-star reviews ](https://wordpress.org/support/plugin/wordsocket/reviews/?filter=4) * [ 0 3-star reviews ](https://wordpress.org/support/plugin/wordsocket/reviews/?filter=3) * [ 0 2-star reviews ](https://wordpress.org/support/plugin/wordsocket/reviews/?filter=2) * [ 0 1-star reviews ](https://wordpress.org/support/plugin/wordsocket/reviews/?filter=1) [Add my review](https://wordpress.org/support/plugin/wordsocket/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/wordsocket/reviews/) ## Contributors * [ wpsignal ](https://profiles.wordpress.org/wpsignal/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/wordsocket/)