SIMPLEPOTRANSLATE
SimplePoTranslate compatibility with REEID Translate
SimplePoTranslate compatibility with REEID Translate is being evaluated from available plugin evidence. Scans a WordPress site to discover translatable theme/plugin projects and translation files (e.g., .po/.pot and untranslated projects) via a recursive scan of active themes and plugins. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for SimplePoTranslate.
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
SimplePoTranslate is documented in the Other category with 8 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 SimplePoTranslate 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
- Scans a WordPress site to discover translatable theme/plugin projects and translation files (e.g., .po/.pot and untranslated projects) via a recursive scan of active themes and plugins.
- Generates and manages gettext translation artifacts by producing .pot templates from theme/plugin source code and importing translated .po files while compiling .mo for use.
- Stores translation outputs in the plugin’s own uploads directory and uses a built-in loader to make WordPress load those translations while the plugin is active.
- Provides an option to copy translations into WordPress’s system language directories (wp-content/languages/plugins/ and wp-content/languages/themes/) so translations can continue loading after the plugin is removed.
- Supports manual translation workflows (download/translate/upload PO files) without requiring an API key.
- Supports optional API-assisted “Auto Translate” where the plugin sends selected PO file contents to the SimplePoTranslate API when an administrator explicitly triggers actions (e.g., Test API Key, opening the dashboard with an API key, and clicking Auto Translate).
- Implements job-based API translation for multiple target languages, including background polling for job status and downloading translated results when jobs complete.
- Creates a .bak backup before importing translations (before importing any translation, it automatically creates a .bak backup of the existing PO file).
CONTENT BOUNDARY
SimplePoTranslate 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
SimplePoTranslate and REEID Translate FAQ.
What does SimplePoTranslate do according to the available plugin evidence?
SimplePoTranslate has 8 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 SimplePoTranslate?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for SimplePoTranslate?
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 SimplePoTranslate in a multilingual WordPress workflow.
REEID documents SimplePoTranslate 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.