OLI IMPORT SYNC FOR TRANSLATEPRESS
Oli Import Sync for TranslatePress compatibility with REEID Translate
Oli Import Sync for TranslatePress compatibility with REEID Translate is being evaluated from available plugin evidence. Imports multilingual content into TranslatePress specifically when used with WP All Import (requires WP All Import Pro). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Oli Import Sync for TranslatePress.
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
Oli Import Sync for TranslatePress 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 Oli Import Sync for TranslatePress 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
- Imports multilingual content into TranslatePress specifically when used with WP All Import (requires WP All Import Pro).
- Supports syncing translated titles, content/descriptions, and excerpts into TranslatePress via WP All Import custom fields (e.g., `_trp_title_[lang]`, `_trp_content_[lang]`, `_trp_excerpt_[lang]`).
- Can import or auto-derive translated post/product slugs from translated titles using `_trp_slug_[lang]` or an auto-derive option; slug translation requires the TranslatePress SEO Pack.
- Supports importing translated WooCommerce category names and slugs (category-name and slug custom fields; slug translation requires the TranslatePress SEO Pack).
- Supports importing translated WooCommerce attribute values and variation descriptions, including variable products and variations.
- Imports multiple languages simultaneously and saves imported translations with status “Human Reviewed” (status 2) to prevent auto-translation from overwriting them.
- Flattens paragraph breaks into a single text block during import so TranslatePress matches one string per description.
- Cleans up temporary custom fields after the import run and updates/overwrites existing translations with the newly imported values (including force-replacing post slug translations).
CONTENT BOUNDARY
Oli Import Sync for TranslatePress 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
Oli Import Sync for TranslatePress and REEID Translate FAQ.
What does Oli Import Sync for TranslatePress do according to the available plugin evidence?
Oli Import Sync for TranslatePress 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 Oli Import Sync for TranslatePress?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Oli Import Sync for TranslatePress?
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 Oli Import Sync for TranslatePress in a multilingual WordPress workflow.
REEID documents Oli Import Sync for TranslatePress 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.