Field Forge – Custom Fields, Relational Fields & Builder
| 开发者 | avakodeforge |
|---|---|
| 更新时间 | 2026年9月18日 23:51 |
| 捐献地址: | 去捐款 |
| 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
安装:
- 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 - Or 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.0.37
- The Forge Suite dashboard links Guard Forge, Velocity Forge and Flow Forge to their sites: guardforge.app, velocityforge.app and flowforgewp.app.
- 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.
- Forge Suite dashboard: results are the first screen — each tool's own results with window and completeness, detected and confirmed apart, a Needs-attention filter and a local CSV export for administrators.
- Set discounts in the Suite banner follow the three-step ladder (2 tools 15%, 3 tools 25%, 4 or more 35%).
- Translations refreshed for all catalogues.
- Licensing no longer depends on a third-party SDK. The plugin asks avakode.com whether this site is licensed and caches the answer for a day; if the check cannot be completed — a network hiccup, a timeout, our own error — your paid features stay on. Only a clear “this licence is not active” turns them off.
- Deactivating from the Forge Suite dashboard now releases the site slot directly, instead of the three-step fallback the old SDK needed when a licence had been cancelled server-side.
- Smaller package and one less admin surface: the SDK’s own menu, opt-in screen and promotional notices are gone.
- Forge Suite dashboard: names of the builder-rail tools (Clearway, Profit, Inclusive Forge) no longer truncate next to the “Not installed” badge.
- The Forge Suite dashboard now shows the whole seven-tool line-up from the product registry — Clearway Forge, Profit Forge and Inclusive Forge join the four WordPress tools — counts active tools against seven, and its cross-sell banner points at the Forge Builder on avakode.com (one checkout, set discount up to 45%) instead of the retired Freemius bundle.
- 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.
- The Bundle License card no longer shows the Connect result twice; translations synced.
- 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.
- Japanese: parentheses in running text are half-width with a space outside, following the Japanese translation style guide. Chinese: parentheses are full-width, as the WordPress core Chinese catalogue writes them.
- 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 load_plugin_textdomain() 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: Opt-in anonymous usage analytics (OFF by default) — see Third-Party Services.
- 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.