ORPHANS
Orphans compatibility with REEID Translate
Orphans compatibility with REEID Translate is being reviewed using official plugin documentation. Automatically replaces spaces after short words with non-breaking spaces when content is displayed, rather than changing stored database content. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Orphans does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Orphans is documented in the Other category with 8 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Orphans compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Automatically replaces spaces after short words with non-breaking spaces when content is displayed, rather than changing stored database content.
- Applies its replacement logic to common front-end content filters such as post titles, excerpts, and content, with settings to limit which post types are processed.
- Supports custom field and arbitrary-string processing through the `orphan_replace` filter.
- Provides configurable orphan-term lists, including the ability to add, remove, or replace default terms via filters and custom term files.
- Includes integration paths for several content builders and field systems, including Bricks, Divi, Muffin/beTheme, WPBakery, Advanced Custom Fields, and Secure Custom Fields.
- Avoids replacement in admin, feeds, and REST API responses.
- Uses protected-tag handling to avoid altering content inside elements such as `pre`, `code`, `iframe`, `svg`, `script`, and `style`.
- Offers settings and capability controls in the WordPress admin, including a dedicated Appearance menu page and a configurable capability filter.
TRANSLATION BOUNDARY
Orphans capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
Orphans and REEID Translate FAQ.
What does Orphans do?
Orphans has 8 documented features listed in its official documentation. See the Plugin Information section for details.
Does Orphans have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Orphans?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Orphans in a multilingual WordPress workflow.
REEID documents Orphans functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.