PLINTH CUSTOM FIELDS
Plinth Custom Fields compatibility with REEID Translate
Plinth Custom Fields compatibility with REEID Translate is being evaluated from available plugin evidence. Self-contained custom fields manager that attaches field groups to post types, page templates, specific pages, or post statuses (via location rules). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Plinth Custom 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
Plinth Custom Fields is documented in the Theme 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 Plinth Custom 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
- Self-contained custom fields manager that attaches field groups to post types, page templates, specific pages, or post statuses (via location rules).
- Provides theme developer template functions to retrieve and render field values and repeater rows/sub-fields inside theme template files (e.g., plinth_get_field(), plinth_the_field(), plinth_get_rows(), plinth_the_row(), plinth_get_sub_field(), plinth_the_sub_field()).
- Supports repeater fields with drag-to-reorder rows and nested sub-fields.
- Implements location rules with AND/OR logic to conditionally show field groups only on matching contexts (post types/pages/templates/statuses).
- Stores all plugin data in standard WordPress post meta (wp_postmeta) using a `_plinth_`-prefixed meta key scheme to avoid collisions.
- Includes JSON import/export for field group configurations to move setups between sites (via Plinth Custom Fields → Import / Export).
CONTENT BOUNDARY
Plinth Custom 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
Plinth Custom Fields and REEID Translate FAQ.
What does Plinth Custom Fields do according to the available plugin evidence?
Plinth Custom Fields 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 Plinth Custom 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 Plinth Custom 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 Plinth Custom Fields in a multilingual WordPress workflow.
REEID documents Plinth Custom 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.