| 开发者 | idanishrangaiz |
|---|---|
| 更新时间 | 2026年8月13日 20:03 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
get_field() and friends working so your theme needs no edits at all.
Beginner-first. A Quick Start wizard sets up your first fields in a few clicks — no need to know what a "custom post type" is. It can even create a matching content type for you, if you want one.
Developer friendly. A full template API, shortcodes, block editor blocks, a REST API, and dozens of action and filter hooks to extend everything.
Field types
Text, Textarea, Number, Email, URL, Password, Select, Multi-Select, Checkbox, Radio, Toggle, True/False, Image, File, Gallery, WYSIWYG, Date, Date & Time, Time, Color, Link, Post Object, Taxonomy, User — plus the advanced Repeater, Group, and Clone fields.
Where fields can appear
Attach field groups by post type, post status, post format, page template, or user role — with multiple rule groups combined using AND/OR logic. Fields render on post, term, and user edit screens and save to standard WordPress meta.
Template API
ozycf_get_field( 'price' ) returns a value, ozycf_the_field( 'price' ) prints it, and repeaters loop cleanly:
if ( ozycf_have_rows( 'slides' ) ) { while ( ozycf_have_rows( 'slides' ) ) { ozycf_the_row(); ozycf_the_sub_field( 'title' ); } }
Also available: ozycf_get_fields(), ozycf_has_field(), ozycf_get_sub_field(), the [ozycf_field] and [ozycf_repeater] shortcodes, and the "OZY Field" and "OZY Repeater" blocks.
Built by OZY Solutions
Learn more at ozysolutions.com.
ozy-custom-fields folder to /wp-content/plugins/, or install through the Plugins screen in WordPress.Not on its own. The plugin makes no external request of any kind until you explicitly use the optional AI features, which call the AI provider you configured with your own API key. Nothing is sent in the background, and there is no telemetry, tracking, or update check. The External Services section documents precisely what is sent, when, and to whom.
No. The AI features are entirely optional — the plugin is fully functional without them. On WordPress 7.0+ they use whatever provider you have connected to WordPress itself, so there is nothing extra to configure here. Otherwise you can use free-tier providers such as Groq or Google Gemini with your own key. Paid providers (OpenAI, Anthropic, Mistral) are also supported if you prefer them.
Yes. Go to Custom Fields → Migrate. The plugin reads what ACF or SCF left in your database and converts your field groups, custom post types, taxonomies, options pages, and every saved field value — free and Pro data alike, including repeaters, groups, flexible content, and conditional logic. Nothing belonging to the other plugin is changed or deleted, so you can deactivate it afterwards and switch back at any time. If your theme calls get_field(), have_rows() or the_sub_field(), tick the compatibility option and those keep working unchanged. No ACF install? Upload the JSON file from its export screen instead.
In standard WordPress meta tables (post, term, and user meta) and in the options table for Options Pages, so they remain accessible via the REST API, WP-CLI, and normal backups. Field group definitions are stored in a dedicated plugin table.
No, unless you explicitly opt in. Deleting the plugin keeps your data by default; a setting under Settings lets you request full cleanup on uninstall.
Yes. Use Tools to export groups as JSON and import them elsewhere, or sync all groups with a local file for version control and staging workflows.
Yes. All strings are translation-ready with the ozy-custom-fields text domain. Translations are contributed and delivered through translate.wordpress.org, so no translation files are bundled with the plugin.
field_0_subfield layout are rebuilt as proper nested rows.acf-json folder) can be converted directly.get_field(), the_field(), get_fields(), have_rows(), the_row(), get_row_layout(), get_sub_field() and the_sub_field() working in your templates so nothing has to be rewritten. It stays dormant while ACF or SCF is still active, so the two never clash.wp ozycf migrate (with --structure-only and --compat).new_field, new_field_2 and so on, because the name stopped following the Field Label as soon as the row was created. New fields now take their name from the label until you edit the name yourself.wp ozycf WP-CLI commands were defined but never registered, so wp ozycf list, export, import and generate were unavailable. They now work, and the Documentation screen shows the correct flags for them.ozycf_ ([ozycf_field], [ozycf_repeater], [ozycf_image], [ozycf_gallery], [ozycf_relationship])..pot template now covers all translatable strings, and the Urdu translation ships compiled so it actually loads.