METABENCH
MetaBench compatibility with REEID Translate
MetaBench compatibility with REEID Translate is being evaluated from available plugin evidence. Custom-field metadata management UI for both post meta and term meta (including search, filter, sort, and in-place editing). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for MetaBench.
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
MetaBench is documented in the Security category with 6 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 MetaBench 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
- Custom-field metadata management UI for both post meta and term meta (including search, filter, sort, and in-place editing).
- Capability-based access control for ordinary meta keys using core `register_meta()` auth callbacks (users who cannot edit via core cannot edit via MetaBench).
- Separate handling for protected meta keys (underscore-prefixed): core `map_meta_cap()` denies `edit_post_meta` for all roles unless a plugin registers a specific `auth_…_meta_…` filter; MetaBench gates protected keys via a settings toggle plus a capability check requiring `manage_options` (filterable via `metabench_protected_capability`).
- REST API endpoints under `metabench/v1` for reading, writing, and deleting individual meta fields (GET/POST/DELETE routes for fields and specific meta IDs).
- Immediate persistence of field edits via the REST API (each field saves independently of the post).
- Developer-extensible security/capability hooks and validation: filters for effective settings/capabilities and a `metabench_validate_key` hook that can return `WP_Error` to block writes.
CONTENT BOUNDARY
MetaBench 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
MetaBench and REEID Translate FAQ.
What does MetaBench do according to the available plugin evidence?
MetaBench has 6 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 MetaBench?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for MetaBench?
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 MetaBench in a multilingual WordPress workflow.
REEID documents MetaBench 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.