CODEIDEAL OPEN FIELDS
Codeideal Open Fields compatibility with REEID Translate
Codeideal Open Fields compatibility with REEID Translate is being reviewed using official plugin documentation. Adds custom fields to posts, pages, custom post types, taxonomies, and users. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Codeideal Open Fields does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Codeideal Open Fields is documented in the Other category with 7 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Codeideal Open Fields compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Adds custom fields to posts, pages, custom post types, taxonomies, and users.
- Provides an ACF-compatible template API with functions such as get_field()/the_field(), get_fields()/update_field()/delete_field(), and have_rows()/the_row()/get_sub_field()/the_sub_field().
- When ACF is also active, Open Fields avoids function conflicts by not loading its ACF-compatible wrappers; both store data as standard WordPress meta and can coexist.
- Supports prefixed API function variants (e.g., cofld_get_field()) that are always available regardless of other plugins.
- Includes field types spanning basic inputs (text/textarea/number/email/url/password), choice inputs (select/checkbox/radio/switch), date & time (date/time/datetime/color picker), media (image/file/gallery), content (WYSIWYG editor/link), relational (post object/taxonomy/user), and layout (repeater/group).
- Allows assigning field groups to location rules including post types (including custom post types), page templates, post status/format/category, taxonomy terms, and user roles.
- Uses a visual admin field-group editor with an interface built from React and TypeScript (admin UI compiled from TypeScript/React source).
TRANSLATION BOUNDARY
Codeideal Open Fields capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
Codeideal Open Fields and REEID Translate FAQ.
What does Codeideal Open Fields do?
Codeideal Open Fields has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does Codeideal Open Fields have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Codeideal Open Fields?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Codeideal Open Fields in a multilingual WordPress workflow.
REEID documents Codeideal Open Fields functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.