FLEX TRANSLATE
Flex Translate compatibility with REEID Translate
Flex Translate compatibility with REEID Translate is being evaluated from available plugin evidence. Provides multilingual support using path-based URLs (e.g., /ru/about, /en/contact) with an option to prefix the default language No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Flex Translate.
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
Flex Translate is documented in the Other 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 Flex Translate 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
- Provides multilingual support using path-based URLs (e.g., /ru/about, /en/contact) with an option to prefix the default language
- Implements text translation helpers for themes/templates: ft('code') to echo translations and ft_get('code') to return translations
- Supports content translations for posts and pages by assigning a language while allowing the same slug across languages (language-specific assignment)
- Includes a language switcher helper function (ft_language_switcher()) with optional flag images
- Translates taxonomy term names and descriptions
- Supports per-language fonts via self-hosted uploads or optional Google Fonts family names; Google Fonts stylesheets are only requested when a Google Font family is configured for a language
- Performs a clean uninstall by removing plugin tables, options, and meta from the WordPress database
CONTENT BOUNDARY
Flex Translate 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
Flex Translate and REEID Translate FAQ.
What does Flex Translate do according to the available plugin evidence?
Flex Translate 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 Flex Translate?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Flex Translate?
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 Flex Translate in a multilingual WordPress workflow.
REEID documents Flex Translate 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.