WORDSOCKET
WordSocket compatibility with REEID Translate
WordSocket compatibility with REEID Translate is being evaluated from available plugin evidence. Realtime event delivery from WordPress to connected browsers via WebSocket, with automatic SSE fallback when WebSocket is unavailable. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for WordSocket.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
WordSocket is documented in the Analytics category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How WordSocket compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Realtime event delivery from WordPress to connected browsers via WebSocket, with automatic SSE fallback when WebSocket is unavailable.
- Publishes encrypted, HMAC-signed realtime events to the WPSignal service when configured triggers fire (e.g., post published, comment approved, option updated, and custom post types).
- Browser-side handling: the client decrypts received payloads and dispatches `wpsignal:*` DOM events; the relay/server is described as not having access to plaintext message content.
- Realtime collaboration integration for Gutenberg: when Gutenberg real-time collaboration is available and enabled, WordSocket registers as a WebSocket-based Yjs sync provider and replaces the default HTTP polling transport for collaborative editing.
- Connection/auth behavior: supports automatic one-click connection via the WPSignal dashboard (no API key required) and manual connection via API key; uses short-lived JWTs (5 minutes) with automatic refresh.
- Per-site isolation and token/channel extensibility: uses per-site JWT signing secrets and supports filters (`wpsignal_token_channels` and `wpsignal_token_channel_prefixes`) to extend token channels and namespace permissions without modifying core.
- Admin controls and diagnostics: includes an admin explorer page with a live event log, publish test event form, and token inspector; includes an admin toggle to disable the collaboration provider and fall back to WordPress HTTP polling.
CONTENT BOUNDARY
WordSocket capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
WordSocket and REEID Translate FAQ.
What does WordSocket do according to the available plugin evidence?
WordSocket has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for WordSocket?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for WordSocket?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate WordSocket in a multilingual WordPress workflow.
REEID documents WordSocket functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.