ONEMETA
OneMeta – Custom Meta Fields compatibility with REEID Translate
OneMeta – Custom Meta Fields compatibility with REEID Translate is being evaluated from available plugin evidence. Visual drag-and-drop builder for creating custom meta field groups No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for OneMeta – Custom Meta Fields.
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
OneMeta – Custom Meta Fields 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 OneMeta – Custom Meta Fields 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
- Visual drag-and-drop builder for creating custom meta field groups
- Live PHP code preview while building field groups
- Export field groups as PHP code so field registration can be used without OneMeta installed
- Repeater fields for repeatable sub-field groups
- Conditional logic to show/hide fields based on other field values using AND/OR rule combinations and operators like ==, !=, contains, and !contains
- REST API support for accessing field data via WordPress REST API on post and user endpoints
- Helper functions for retrieving field values in themes: onemeta_get_meta(get_the_ID(), 'field_key') and onemeta_get_user_meta($user_id, 'field_key')
CONTENT BOUNDARY
OneMeta – Custom Meta Fields 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
OneMeta – Custom Meta Fields and REEID Translate FAQ.
What does OneMeta – Custom Meta Fields do according to the available plugin evidence?
OneMeta – Custom Meta Fields 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 OneMeta – Custom Meta Fields?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for OneMeta – Custom Meta Fields?
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 OneMeta – Custom Meta Fields in a multilingual WordPress workflow.
REEID documents OneMeta – Custom Meta Fields 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.