FIELDSTONE
Fieldstone compatibility with REEID Translate
Fieldstone compatibility with REEID Translate is being evaluated from available plugin evidence. Stores Fieldstone field values in dedicated, indexed database tables (one row per post) rather than only using `wp_postmeta`. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Fieldstone.
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
Fieldstone 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 Fieldstone 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 Fieldstone field values in dedicated, indexed database tables (one row per post) rather than only using `wp_postmeta`.
- Maintains a postmeta mirror (enabled by default) so other WordPress ecosystem components that expect postmeta can still access values; includes a rebuild tool for both directions.
- Provides a visual editor to define field groups, including custom post types and taxonomies, with location rules that target where groups appear (e.g., by post type, template, specific post/page, page type, post status, user role, taxonomy, attachment type, or menu item).
- Renders front-end forms via `fstn_form()` with server-side submission handling including validation, a honeypot, and rate limiting; the form targets are stored on the server.
- Exposes field values to themes via template/developer functions such as `fstn_get_field()`, `fstn_the_field()` (escaped by default), `fstn_get_fields()`, `fstn_update_field()`, and `fstn_delete_field()`, with support for multiple contexts (post ID, `option`, user, term, or WP objects).
- Supports conditional logic and validation rules for fields, with server-side enforcement (including required fields and constraints like length/range/pattern/format).
- Offers REST API integration by opting field groups into the REST API so values appear on post responses and can be written with proper permissions.
- Includes import/export and developer tooling: duplicate/import/export of groups (JSON/PHP), WP-CLI commands (`wp fstn json status|sync`, `wp fstn mirror rebuild`, `wp fstn table status`), and local JSON syncing for definitions.
CONTENT BOUNDARY
Fieldstone 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
Fieldstone and REEID Translate FAQ.
What does Fieldstone do according to the available plugin evidence?
Fieldstone 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 Fieldstone?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Fieldstone?
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 Fieldstone in a multilingual WordPress workflow.
REEID documents Fieldstone 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.