| 开发者 | avakodeforge |
|---|---|
| 更新时间 | 2026年8月13日 20:51 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
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
wp_postmeta)get_field() / update_field()fieldforge to /wp-content/plugins/, or install via Plugins → Add New.$value = get_field('my_field', $post_id);GET /wp-json/wp/v2/posts/123/fieldforgeposts { nodes { fieldforge { myField } } }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.
The opposite — values are not autoloaded from wp_postmeta. Listing 100 posts with 50 fields each loads in ms instead of seconds.
No. Native WPGraphQL schema is built-in (Pro). You don't need "WPGraphQL for ACF" or similar bridge plugins.
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).