Field Forge – Custom Fields, Relational Fields & Builder
| 开发者 | avakodeforge |
|---|---|
| 更新时间 | 2026年10月16日 00:49 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Field Forge is a modern custom-fields plugin. Fields live in dedicated tables (
wp_fieldforge_values) instead of the bloated wp_postmeta, so listing pages stay fast even with 50+ fields per post. Drag-drop the field group editor, then read values via PHP or REST.
Free
- Unlimited field groups
- 31 field types — text, textarea, number, select, image, file, WYSIWYG, oEmbed, Gallery, Calculation, date/time/color pickers, Google Map, link, and the relational set (Relationship, Post Object, Page Link, Taxonomy, User)
- Location rules (post type, taxonomy, template, user role)
- ACF compatibility layer (import existing ACF groups + values)
- Custom-table storage (not
wp_postmeta) - Migration UI from ACF Free
- Visual field group builder
- Local JSON sync (write field groups to disk for version control)
- Options-page values via
get_field()/update_field() - REST API field exposure
- Schema versioning + revision history for field groups
- Compound field types: Repeater, Group, Flexible Content, Clone
- Options pages management screen (creating and editing the pages themselves)
- PHP Blocks (register Gutenberg blocks from field groups)
- AI schema generator (describe the data → generates a field group)
- Native WPGraphQL schema + resolvers (no add-on plugin needed)
- TypeScript / JSON sync (export field groups to your repo)
- Bulk JSON export / import
- Priority email support with an active Pro licence
安装:
- Upload
fieldforgeto/wp-content/plugins/, or install via Plugins → Add New. - Activate the plugin.
- Go to Field Forge → Field Groups → New Field Group.
- Read values in PHP:
$value = get_field('my_field', $post_id); - Or via REST:
GET /wp-json/wp/v2/posts/123/fieldforge - With the separate Field Forge Pro add-on, also via GraphQL:
posts { nodes { fieldforge { myField } } }
屏幕截图:
常见问题:
Can I migrate from ACF?
Yes. Field Forge → Migration → ACF detects existing field groups + values and imports them into Field Forge tables. The ACF compat layer keeps your get_field() calls working during migration.
Will it slow down my admin?
The opposite — values are not autoloaded from wp_postmeta. Listing 100 posts with 50 fields each loads in ms instead of seconds.
Is GraphQL support a separate add-on?
No. Native WPGraphQL schema is built-in (Pro). You don't need "WPGraphQL for ACF" or similar bridge plugins.
更新日志:
1.1.6
- Text and Textarea fields get a Character limit setting: the box stops at the limit, and a text over it is not saved. The field keeps its previous value and you see a notice. With Field Forge Pro 1.1.14 the limit also holds inside Repeater, Group and Flexible Content fields and on options pages.
- Character limits already stored in your field groups (an ACF import, the SEO Settings template) now take effect. A saved text that is already longer is kept, with a note under the field.
- Checkbox and Radio fields get a Layout setting: vertical or horizontal.
- The Post Template location rule offers a list of your theme's templates instead of a text box.
- Field group editor: location rules can now be set by Post Category and Post Taxonomy term. Categories with the same name under different parents are listed as "Parent › Name".
- Fixed: Post Category and Post Taxonomy rules imported from ACF now apply to the right posts. A rule on a term that no longer exists matches no post.
- Fixed: a rule on a term with a non-Latin slug is no longer broken when the group is saved in the editor.
- On the new-post screen, a field group with a Post Category or Post Taxonomy rule is shown only when the new post fits the rule (a new post counts as being in the default category). Before, such a group was shown on every new post of its post type when it also had a Post Type rule, and was not shown at all when it had none.
- With the Field Forge Pro add-on: the sub-fields of a Repeater, Group or Flexible Content field now have Choices, Instructions and Placeholder settings in the group editor, and the edit screen shows them. Choices work for Select, Checkbox, Radio and Button Group, Placeholder for Text, Textarea, Number, Email, URL and Password. Before, a Select, Checkbox or Radio sub-field was drawn as a plain text box and had nowhere to enter its choices. A sub-field of a choice type with no choices entered is still a text box.
- Button Group is now in the sub-field type list. In a Button Group sub-field only the picked button looks pressed, and "Add Row" starts the new row with nothing picked in Radio, Checkbox and Button Group sub-fields.
- A value a row already holds that is not one of the sub-field's choices (for example text saved while the sub-field was still a text box) is shown as one more picked choice, and Update keeps it. A stored list is shown as text in a Textarea sub-field and as a picked choice in a Radio or Select sub-field.
- Dragging a Repeater or Flexible Content row no longer clears the picked Radio or Button Group choice in the other rows.
- ACF import: Clone fields keep their settings and targets; a target that was not imported is left out and named in the result.
- ACF import with Field Forge Pro (licence active): settings pages made in ACF 6.2+ or registered in code while ACF is active are created, and the values step copies their values for regular, Group and Repeater fields. Values already saved in Field Forge, including a Repeater's row count, are kept. A page that could not be created is named in the result.
- ACF import without Field Forge Pro: Repeater, Group, Flexible Content and Clone fields are no longer created; the rest of the group is imported and the result lists what was left out. A group made only of such fields is not imported.
- Fixed: a Clone field whose target field sits in a later field group, or lower in its own group, no longer breaks field lookups.
- Fixed (with the Field Forge Pro add-on): a Group in a Flexible Content row added with "Add Layout" lost the values typed into it on the first Update.
- After you rename a field and save the group, the saved values on your posts now show under the new name right away. Before, they could keep showing under the old name for up to five minutes, until the short-lived cache expired. On a site with more than 2000 affected posts it can still take up to five minutes.
- A True/False field whose Default is no, false or off (capitals and spaces around the word do not matter) is no longer shown switched on before its first save. Before, any text in Default switched it on, including "no". An empty Default or 0 still means off; any other text still means on.
- Importing values from ACF now converts a Date Picker value from the format ACF stores (20261011) to the format Field Forge shows and saves (2026-10-11). Before, an imported date showed as an empty date box. Dates imported earlier are not changed.
- With the Field Forge Pro add-on (1.1.10 or newer): a Repeater inside a Flexible Content layout you have just added now appears at once with its Add Row button. Before, it was only a label, and rows could not be added to it in the editor. A Flexible Content field inside the new layout is drawn the same way.
- Changing the Label of a field that is already saved no longer changes its Name. Before, the Name followed the Label, and saving the group renamed the field. A field you have just added still takes its Name from its Label until you type a Name yourself, and typing a new Name in a saved field still renames it.
- A Date Picker value saved without dashes, such as 20261011 (the way ACF stores dates), is now saved as 2026-10-11 and shown in the date box. Before, the date box looked empty, and updating the post erased the date.
- The Cmd/Ctrl + Shift + F shortcut for Add Field in the field group editor now opens the Add Field window. With Shift held the browser reports the key as a capital F, and the shortcut only recognised a small f, so nothing happened.
- Local JSON Sync writes field group files only inside the uploads folder (uploads/fieldforge-json by default) and no longer reads /fieldforge-json on its own. Groups saved from the site are in the database and are not affected. Groups that exist only as JSON in the theme folder stay on disk but are not listed until you add the folder with the fieldforge/local_json/load_paths filter and sync. A save path outside uploads falls back to the default; files already there are not moved.
- The ACF importer asks ACF where its Local JSON folders are, instead of working out the theme folder itself.
- Adding a Flexible Content row (a field type of the Field Forge Pro add-on) no longer leaves an output buffer open when one of its field renderers fails.
- The empty Field Groups list now says how many ACF field groups it found on the site and links to the migration screen. Only that screen, and only while the list is empty, looks for them, and only administrators see the note.
- Deleting the plugin leaves the job queue the Forge plugins share in place while another Forge plugin or add-on is still on the site. The check used to miss add-ons, and Rank Forge installed from wordpress.org, so the queue could be dropped while a neighbour still had jobs in it.
- This release needs Field Forge Pro 1.1.5 or newer if you run the add-on. The licence screen, the upgrade prompt and the upgrade banner moved into the separate Field Forge Pro add-on; this plugin only notes which screens the add-on provides, with a link to its product page. An older add-on stays switched off until it is updated: the Pro field types, Options Pages, the REST and GraphQL exposure and the AI actions stop, nothing already saved is changed, and an admin notice names both versions.
- The Options Pages screen and the JSON export and import on the Tools screen say that they belong to the add-on instead of showing a locked page.
- The "matches pattern" condition no longer changes PHP's regular-expression limits while it runs. A pattern that would run away is still stopped by PHP and treated as not matching.
- Options Pages management and the clone field check for the Field Forge Pro add-on at every place they use it. Nothing changes on a site with or without it.
- No change in this package: the release updated parts that ship only in the edition distributed through avakode.com.
- This release needs Field Forge Pro 1.1.0 or newer. An older add-on is switched off whole rather than left running, because beside this core it would be present and wrong rather than absent. Until you update it the Pro field types Repeater, Group, Flexible Content and Clone, Options Pages, the REST and GraphQL exposure and the AI actions are unavailable. Nothing already saved is changed, an admin notice names both versions and what stopped, and installing the current add-on brings all of it back.
- Deleting the last Forge product on a site now clears the job queue the Forge plugins share — its table, its two scheduled events and its version marker. While any other Forge product is still installed, deleting this one leaves the queue exactly as it is, because the pending jobs in those rows are that product's too.
- Fixed: in a group laid out in columns, the buttons under an image field ran past the column and the "Remove" button was cut in half. They wrap now, and the preview never outgrows the column it sits in.
- Fixed: posts saved by 1.0.25–1.0.33 could hold a nested Group, Repeater or Flexible Content as a separate top-level field, which left it out of its parent group in the editor. Updating moves those records back where they belong, in the background. The repair only moves a record whose parent is unambiguous and already on the post; anything it cannot prove it leaves exactly as it is.
- Fixed: on a site migrated from ACF the post editor drew every custom field empty while the site itself still rendered the values, and pressing Update then blanked the page. The editor now reads the same values the site reads, and the first save moves them into Field Forge's own storage.
- Fixed: a Repeater, Group or Flexible Content nested inside a group could be saved as a separate top-level field, so it disappeared from its parent.
- Fixed: values in a Group, Repeater or Flexible Content field were dropped when a post was saved from the editor — an image picked into a group showed its preview and was empty again after Update. Simple fields were never affected. Introduced in 1.0.25; if you saved compound fields since then, re-enter and save those values once.
- No change in this package: the release updated parts that ship only in the edition distributed through avakode.com.
- Smaller package and one less admin surface: the SDK’s own menu, opt-in screen and promotional notices are gone.
- No change in this package: the release updated parts that ship only in the edition distributed through avakode.com.
- No change in this package: the release updated parts that ship only in the edition distributed through avakode.com.
- The shared inline assets (docs link, feedback widget) are now emitted as a literal nowdoc block instead of being assembled in an output buffer — the same hardening Lang Forge 1.0.31 and Rank Forge 1.1.3 received.
- Lang Forge is detected by its current class name (LANGFORGE_Core), so field-value language sync, the migration helper and the shared dashboard cards keep working with Lang Forge 1.0.31 and later.
- Declares support for WordPress 7.1. Checked against 7.1-RC3: the field-group builder's drag-and-drop still works there, jQuery UI having gone to 1.14.2.
- The sibling plugin formerly called SEO Forge is now Rank Forge, so the shared Forge screens and the cross-links name it correctly.
- The directory listing now names what the plugin does alongside the brand, matching how Lang Forge is listed. The plugin, its folder and its URL are unchanged — only the displayed title.
- Fixed a database error printed on every activation. The longtext and text columns were declared with DEFAULT '', which MySQL does not allow on BLOB/TEXT, so dbDelta kept trying to set it and failed loudly. Found by activating with WP_DEBUG on a clean install.
- Local JSON now writes only to the uploads directory. A theme folder is no longer a write target even when the developer created one — wp-content/themes is not a location a plugin may write to. Files already committed under a theme are still read, so existing setups keep working; a filtered save path that points at a theme, plugin or core directory falls back to uploads.
- The metabox save path no longer passes the whole request array on. Only this plugin's own submitted values are read, reduced to the fields that belong to the post, and each is sanitized by its declared field type before anything downstream sees it.
- Renamed the two ACF-migration options off the reserved "fdf" prefix onto "fieldforge_". Existing values, including the ACF-group id map, are carried over by a schema migration, so a site that already imported from ACF does not re-import duplicates.
- ACF's own hooks are consulted only when ACF is actually active.
- The Gallery field and the Calculation field are now part of this plugin with no restriction. Both were marked Pro while their implementations shipped here, which meant built-in functionality was gated — that was wrong and is fixed.
- Options-page values, the Import / Export screen and the ACF importer are likewise unrestricted. Nothing shipped in this download is withheld any more: features that genuinely belong to the separate Pro add-on are detected by whether that plugin is installed, not by a licence check.
- Field definitions received over AJAX and REST are now sanitized key by key before storage, instead of only their conditional-logic block.
- oEmbed previews are escaped at the output site with an explicit tag allowlist.
- Local JSON now writes to the uploads directory by default and never creates a directory inside a theme. An existing /fieldforge-json is still used when the developer has created one.
- Admin CSS moved out of inline blocks into the enqueued stylesheet.
- Removed the red counter bubble on the License menu item — it reused core's update-notification styling.
- Field-group schema REST reads now require manage_options, and the aggregate endpoint no longer accepts an arbitrary post status.
- Dropped the manual text-domain loading call; WordPress loads the translations by itself.
- Security hardening: all dynamic output is now escaped late at the output site with the context-appropriate function (esc_html/esc_attr/esc_url, esc_html__ for translated strings used as format strings, and wp_kses for trusted pre-built admin/field markup). No behavioural changes.
- Local JSON sync is now available on the Free plan (like ACF's Local JSON) — enabled by the setting alone, no license required.
- ACF value migration (importing existing ACF field values) is now available on the Free plan.
- Field values are now exposed on the standard REST post endpoints for every plan (opt-in per field).
- Removed the leftover license-gated field-group count limit and its "locked" UI — Free has always supported unlimited field groups.
- New: Support menu item that opens the Avakode support dashboard.
- New: Contextual, dismissible Pro feature tips on the plugin dashboard (Free users only).
- New (Pro): Calculation field — compute a total from a formula over sibling fields ({price} * {qty}) or by summing a numeric sub-field across repeater rows, with number/currency/percentage formatting and a live per-keystroke preview.
- New (Free): [fieldforge_total] shortcode and fieldforge_aggregate_field() to total a numeric field across posts; REST /aggregate and GraphQL fieldForgeAggregate (Pro).
- Accessibility: Button Group field radios are now keyboard- and screen-reader-accessible. They were hidden with
display:none, which removed them from the tab order and accessibility tree; they are now visually hidden the accessible way (the visible button label still toggles the selection).
- WordPress.org compliance and licensing hardening.
- Pro entitlement is now resolved by the Field Forge Pro add-on; the free plugin bundles no licensing SDK.
- readme metadata cleanup.
- Initial release.