POLYGLOT TRANSLATE CONNECTOR
Polyglot Translate Connector compatibility with REEID Translate
Polyglot Translate Connector compatibility with REEID Translate is being evaluated from available plugin evidence. Registers Polyglot Translate Connector as a `translation`-type connector in the WordPress 7.0 Connectors registry. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Polyglot Translate Connector.
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
Polyglot Translate Connector is documented in the Other 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 Polyglot Translate Connector 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
- Registers Polyglot Translate Connector as a `translation`-type connector in the WordPress 7.0 Connectors registry.
- Adds a Polyglot card to the WordPress admin screen **Settings → Connectors**, including a credential field for the Polyglot Translate API key.
- Validates the API key against Polyglot Cloud on save by performing a `GET /v1/health` preflight check; if the cloud is unreachable, it warns (does not block).
- Exposes stable PHP helper functions (e.g., `polyglot_get_api_key()`, `polyglot_is_connected()`, `polyglot_get_api_base_url()`) intended for other plugins on the site to consume Polyglot credentials transparently.
- Adds a Site Health check to verify and display the connection state for the connector.
- Supports credential configuration via environment variables and PHP constants (in addition to the database option set in **Settings → Connectors**), with documented precedence: env var `POLYGLOT_TRANSLATE_API_KEY`, then PHP constant `POLYGLOT_TRANSLATE_API_KEY`, then database option.
- Provides an optional advanced setting to override the Polyglot API base URL via **Settings → Polyglot Translate** (HTTPS-only), intended for self-hosted/reverse-proxy/staging scenarios.
CONTENT BOUNDARY
Polyglot Translate Connector 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
Polyglot Translate Connector and REEID Translate FAQ.
What does Polyglot Translate Connector do according to the available plugin evidence?
Polyglot Translate Connector 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 Polyglot Translate Connector?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Polyglot Translate Connector?
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 Polyglot Translate Connector in a multilingual WordPress workflow.
REEID documents Polyglot Translate Connector 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.