OZY CUSTOM FIELDS
OZY Custom Fields compatibility with REEID Translate
OZY Custom Fields compatibility with REEID Translate is being evaluated from available plugin evidence. Visual field-group builder with flexible location rules (AND/OR rule groups) to attach field groups to post type/status/format, page template, or user role. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for OZY 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
OZY Custom Fields 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 OZY 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
- Visual field-group builder with flexible location rules (AND/OR rule groups) to attach field groups to post type/status/format, page template, or user role.
- Advanced field types including Repeater, Group, and Clone, plus many basic input types (e.g., text, textarea, number, select, image/file/gallery, WYSIWYG, date/time, color, link, post object, taxonomy, user).
- Front-end template API and rendering helpers for retrieving/printing fields and iterating repeater rows (e.g., `ozycf_get_field`, `ozycf_the_field`, `ozycf_have_rows`, `ozycf_the_row`, `ozycf_the_sub_field`).
- Admin-side developer interfaces: shortcodes, block editor blocks (OZY Field / OZY Repeater blocks), and a REST API plus action/filter hooks for extensibility.
- Optional AI Field Generator that drafts field groups from a plain-language description (English or Urdu) and can use either WordPress 7.0+ AI Client via WordPress connectors or a user-supplied provider key; AI requests occur only when an admin AI action is triggered.
- Migration/import capability from Advanced Custom Fields (ACF) or Secure Custom Fields (SCF), including conversion of field groups, custom post types, taxonomies, options pages, and saved field values; includes an optional compatibility layer for `get_field()`-style calls.
- Data storage behavior: field values are stored in standard WordPress meta tables (post/term/user meta) and options table for Options Pages; field group definitions are stored in a dedicated plugin table; uninstall keeps data by default unless an explicit cleanup option is enabled.
CONTENT BOUNDARY
OZY 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
OZY Custom Fields and REEID Translate FAQ.
What does OZY Custom Fields do according to the available plugin evidence?
OZY Custom Fields 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 OZY 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 OZY 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 OZY Custom Fields in a multilingual WordPress workflow.
REEID documents OZY 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.