DYNAMIC FIELDS ENGINE
Dynamic Fields Engine – Custom post types, Custom fields, Meta fields, Taxonomies, Listing builder, Query builder and Relations compatibility with REEID Translate
Dynamic Fields Engine – Custom post types, Custom fields, Meta fields, Taxonomies, Listing builder, Query builder and Relations compatibility with REEID Translate is being evaluated from available plugin evidence. Custom post type creation and configuration (labels, supports, REST visibility, archive behavior, permalink/rewrite settings, capability type, menu placement) via an admin UI. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Dynamic Fields Engine – Custom post types, Custom fields, Meta fields, Taxonomies, Listing builder, Query builder and Relations.
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
Dynamic Fields Engine – Custom post types, Custom fields, Meta fields, Taxonomies, Listing builder, Query builder and Relations 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 Dynamic Fields Engine – Custom post types, Custom fields, Meta fields, Taxonomies, Listing builder, Query builder and Relations 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
- Custom post type creation and configuration (labels, supports, REST visibility, archive behavior, permalink/rewrite settings, capability type, menu placement) via an admin UI.
- Custom taxonomies with hierarchical or flat types, including taxonomy term meta fields and configurable REST visibility/rewrite rules, plus admin column display and taxonomy templates.
- Meta boxes / custom fields system with multiple field types (e.g., text/textarea/number/email/url/date/time/color/select/checkbox/radio/toggle/image/file/WYSIWYG, plus advanced types like group/repeater/relationship/taxonomy picker/user picker/tab/accordion/endpoint/html) and location rules to target where field groups appear in WP admin.
- Import/export and configuration portability using JSON bundles, including diff preview, slug conflict resolution, and snapshot rollback.
- Saved queries and listing templates: visual query builder for posts/terms/users (including taxonomy/meta query operators and ordering), and a drag-and-drop listing engine with listing types (card/grid/single page/archive page) and dynamic components.
- Post relations between WordPress objects (posts/terms/users) supporting one-to-one/one-to-many/many-to-many, with connection-specific custom fields, relation inheritance/hierarchy behavior, and dedicated storage for efficient queries.
- Developer-oriented configuration APIs: PHP registration API for post types/taxonomies/field groups and a REST-first config API with CRUD endpoints, plus export of configurations as drop-in PHP code for theme bundling/version control.
CONTENT BOUNDARY
Dynamic Fields Engine – Custom post types, Custom fields, Meta fields, Taxonomies, Listing builder, Query builder and Relations 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
Dynamic Fields Engine – Custom post types, Custom fields, Meta fields, Taxonomies, Listing builder, Query builder and Relations and REEID Translate FAQ.
What does Dynamic Fields Engine – Custom post types, Custom fields, Meta fields, Taxonomies, Listing builder, Query builder and Relations do according to the available plugin evidence?
Dynamic Fields Engine – Custom post types, Custom fields, Meta fields, Taxonomies, Listing builder, Query builder and Relations 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 Dynamic Fields Engine – Custom post types, Custom fields, Meta fields, Taxonomies, Listing builder, Query builder and Relations?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Dynamic Fields Engine – Custom post types, Custom fields, Meta fields, Taxonomies, Listing builder, Query builder and Relations?
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 Dynamic Fields Engine – Custom post types, Custom fields, Meta fields, Taxonomies, Listing builder, Query builder and Relations in a multilingual WordPress workflow.
REEID documents Dynamic Fields Engine – Custom post types, Custom fields, Meta fields, Taxonomies, Listing builder, Query builder and Relations 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.