CONTENTGECKO CONNECTOR
ContentGecko Connector compatibility with REEID Translate
ContentGecko Connector compatibility with REEID Translate is being evaluated from available plugin evidence. Secure REST API access protected by a shared API key header (`X-ContentGecko-Key`) with the stored key hashed using `hash_hmac()` (with `AUTH_SALT`). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for ContentGecko 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
ContentGecko Connector is documented in the Security 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 ContentGecko 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
- Secure REST API access protected by a shared API key header (`X-ContentGecko-Key`) with the stored key hashed using `hash_hmac()` (with `AUTH_SALT`).
- Optional inbound IP allow-listing via an allow-list filter (`contentgecko_allowed_ips`) to restrict requests by source IP.
- Capability checks inside `wp-admin` for REST operations (described as “tight capability checks inside wp-admin”).
- REST endpoints for publishing/updating content: posts via `/wp-json/contentgecko/v1/posts` and pages via `/wp-json/contentgecko/v1/pages`, with sanitising of content and metadata using WordPress core helpers.
- Remote featured image sideloading using WordPress core upload handlers with MIME restriction, reusing existing attachments when possible.
- Optional debug logging that persists the last 50 REST calls and exposes recent request metadata in the WordPress admin settings screen; logging is disabled by default.
- Multilingual content mapping that links translations and respects the site’s default language when WPML or Polylang are present (described as “Map multilingual content to WPML or Polylang”).
CONTENT BOUNDARY
ContentGecko 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
ContentGecko Connector and REEID Translate FAQ.
What does ContentGecko Connector do according to the available plugin evidence?
ContentGecko 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 ContentGecko 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 ContentGecko 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 ContentGecko Connector in a multilingual WordPress workflow.
REEID documents ContentGecko 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.