FIELD FORGE
Field Forge – Custom Fields, Relational Fields & Builder compatibility with REEID Translate
Field Forge – Custom Fields, Relational Fields & Builder compatibility with REEID Translate is being evaluated from available plugin evidence. Stores custom field values in dedicated database tables (e.g., `wp_fieldforge_values`) rather than `wp_postmeta`. No specific visitor-facing translation surface is currently confirmed.
Visit Field Forge – Custom Fields, Relational Fields & Builder ↗
AWAITING VERIFICATION
What the available evidence establishes for Field Forge – Custom Fields, Relational Fields & Builder.
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
Field Forge – Custom Fields, Relational Fields & Builder 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 Field Forge – Custom Fields, Relational Fields & Builder 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
- Stores custom field values in dedicated database tables (e.g., `wp_fieldforge_values`) rather than `wp_postmeta`.
- Provides a field-group editor with drag-and-drop visual building for defining field groups.
- Supports an ACF compatibility layer, including importing existing ACF field groups/values and maintaining `get_field()` compatibility during migration.
- Exposes field values via REST API endpoints (example given: `GET /wp-json/wp/v2/posts/123/fieldforge`).
- Provides native WPGraphQL schema/resolvers for field exposure (described as built-in with Pro).
- Implements local JSON sync for field groups (write field groups to disk for version control).
- Includes an opt-in anonymous usage telemetry mechanism (OFF by default) that sends only aggregate feature-usage counters and version/bucket ranges to the Avakode API after opt-in, without sending site URL, email, post/form content, or license key.
CONTENT BOUNDARY
Field Forge – Custom Fields, Relational Fields & Builder 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
Field Forge – Custom Fields, Relational Fields & Builder and REEID Translate FAQ.
What does Field Forge – Custom Fields, Relational Fields & Builder do according to the available plugin evidence?
Field Forge – Custom Fields, Relational Fields & Builder 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 Field Forge – Custom Fields, Relational Fields & Builder?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Field Forge – Custom Fields, Relational Fields & Builder?
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 Field Forge – Custom Fields, Relational Fields & Builder in a multilingual WordPress workflow.
REEID documents Field Forge – Custom Fields, Relational Fields & Builder 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.