CUSTOM METADATA MANAGER
Custom Metadata Manager compatibility with REEID Translate
Custom Metadata Manager compatibility with REEID Translate is being evaluated from available plugin evidence. Code-based API to register custom metadata fields and groups for multiple WordPress object types (posts, pages, custom post types, users, and comments). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Custom Metadata Manager.
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
Custom Metadata Manager is documented in the Other category with 5 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 Custom Metadata Manager 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
- Code-based API to register custom metadata fields and groups for multiple WordPress object types (posts, pages, custom post types, users, and comments).
- Stores custom fields using the standard WordPress metadata APIs and keeps the data available even if the plugin is later deactivated.
- Renders fields in metaboxes (for supported object types) and supports built-in field types or developer-supplied display and sanitisation callbacks.
- Supports including/excluding specific fields and groups for particular objects either by ID or via callback rules.
- Provides multifield support and a developer-focused documentation set (DEVELOPERS.md and worked examples) for defining object types, field/group registration, and include/exclude logic.
CONTENT BOUNDARY
Custom Metadata Manager 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
Custom Metadata Manager and REEID Translate FAQ.
What does Custom Metadata Manager do according to the available plugin evidence?
Custom Metadata Manager has 5 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 Custom Metadata Manager?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Custom Metadata Manager?
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 Custom Metadata Manager in a multilingual WordPress workflow.
REEID documents Custom Metadata Manager 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.