| 开发者 | idanishrangaiz |
|---|---|
| 更新时间 | 2026年7月29日 19:19 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
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.
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.
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.