NATIVE CUSTOM FIELDS
Native Custom Fields – Custom Content Types and Meta Fields compatibility with REEID Translate
Native Custom Fields – Custom Content Types and Meta Fields compatibility with REEID Translate is being evaluated from available plugin evidence. Creates custom content types (custom post types) and custom taxonomies using WordPress native components. No specific visitor-facing translation surface is currently confirmed.
Visit Native Custom Fields – Custom Content Types and Meta Fields ↗
AWAITING VERIFICATION
What the available evidence establishes for Native Custom Fields – Custom Content Types and 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
Native Custom Fields – Custom Content Types and Meta Fields is documented in the Other category with 8 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 Native Custom Fields – Custom Content Types and 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
- Creates custom content types (custom post types) and custom taxonomies using WordPress native components.
- Provides meta field groups that can be attached to post types, taxonomies, user profiles, and options pages.
- Stores configuration in `wp_options` and stores field data in standard WordPress meta tables (postmeta/termmeta/usermeta), and does not create custom database tables or hidden configuration post types.
- Supports import/export of configuration via JSON or PHP.
- Includes an options page and a fields builder for defining field groups and fields.
- Offers a set of supported field/input components (e.g., text, number, select, checkbox, radio, textarea, date/time pickers, media/file upload, and custom components like Repeater and Group).
- Provides a modern React-based admin UI built with WordPress native component packages (e.g., `@wordpress/components`, `@wordpress/data`, `@wordpress/elements`, etc.).
- Includes an AI integration described as using an “Abilities API” and a “WordPress AI Client.”
CONTENT BOUNDARY
Native Custom Fields – Custom Content Types and 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
Native Custom Fields – Custom Content Types and Meta Fields and REEID Translate FAQ.
What does Native Custom Fields – Custom Content Types and Meta Fields do according to the available plugin evidence?
Native Custom Fields – Custom Content Types and Meta Fields has 8 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 Native Custom Fields – Custom Content Types and 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 Native Custom Fields – Custom Content Types and 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 Native Custom Fields – Custom Content Types and Meta Fields in a multilingual WordPress workflow.
REEID documents Native Custom Fields – Custom Content Types and 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.