GLOTY
Gloty – AI Translation & Multilingual compatibility with REEID Translate
Gloty – AI Translation & Multilingual compatibility with REEID Translate is being evaluated from available plugin evidence. Local, render-time deterministic serving: translated pages are served from the site’s own WordPress database with no remote call at render time. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Gloty – AI Translation & Multilingual.
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
Gloty – AI Translation & Multilingual is documented in the Performance 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 Gloty – AI Translation & Multilingual 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
- Local, render-time deterministic serving: translated pages are served from the site’s own WordPress database with no remote call at render time.
- OPcache-backed compiled PHP cache (“compiled map”): Gloty compiles translations (and glossary) into a PHP cache file intended to be held in server OPcache shared memory, aiming to avoid database queries for translation during warmed page views.
- Graceful fallback when compiled cache isn’t available: if OPcache is unavailable/restricted, uploads isn’t writable, or the cache file is damaged, Gloty serves translations from the database instead (with correctness preserved, performance reduced).
- Background translation pipeline with queued dispatch and webhook/polling: translation work is queued and processed in the background; results are delivered back to the site via a signed webhook with a polling fallback.
- External translation requests are routed through the Gloty translator service: the plugin sends source text, source/target language codes, site URL, and per-site token/license to the hosted Gloty translator service (service host `https://gloty-api.wp-shelf.com`, overridable via `GLOTY_SERVICE_URL`).
- WordPress.org language pack installation for enabled locales: when enabling a language, Gloty triggers WordPress core’s updater to install official WordPress and plugin language packs for that locale (without sending site content).
- Cache file write location and non-browsable protection: compiled cache files are written into a `gloty-cache` folder inside the uploads directory (with a `wp-content/cache/gloty` fallback), and the folder includes `index.php` and `.htaccess` to prevent direct browsing and direct output.
CONTENT BOUNDARY
Gloty – AI Translation & Multilingual 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
Gloty – AI Translation & Multilingual and REEID Translate FAQ.
What does Gloty – AI Translation & Multilingual do according to the available plugin evidence?
Gloty – AI Translation & Multilingual 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 Gloty – AI Translation & Multilingual?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Gloty – AI Translation & Multilingual?
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 Gloty – AI Translation & Multilingual in a multilingual WordPress workflow.
REEID documents Gloty – AI Translation & Multilingual 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.