Title: Field Forge – Custom Fields, Relational Fields & Builder Author: avakodeforge Published: আগষ্ট 7, 2026 Last modified: অক্টোবৰ 6, 2026 --- প্লাগিনৰ সন্ধান কৰক ![](https://ps.w.org/fieldforge/assets/banner-772x250.png?rev=3637549) ![](https://ps.w.org/fieldforge/assets/icon-256x256.png?rev=3637549) # Field Forge – Custom Fields, Relational Fields & Builder [avakodeforge](https://profiles.wordpress.org/avakodeforge/)-ৰ দ্বাৰা [ডাউনল’ড কৰক](https://downloads.wordpress.org/plugin/fieldforge.1.0.41.zip) * [বিশদ বিৱৰণ](https://as.wordpress.org/plugins/fieldforge/#description) * [পৰ্য্যালোচনা](https://as.wordpress.org/plugins/fieldforge/#reviews) * [ইনষ্টলেশ্যন](https://as.wordpress.org/plugins/fieldforge/#installation) * [বিকাশ](https://as.wordpress.org/plugins/fieldforge/#developers) [সাহায্য](https://wordpress.org/support/plugin/fieldforge/) ## বৰ্ণনা **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 #### Field Forge Pro Pro is a separate add-on plugin, distributed from https://fieldforgewp.com and not included in this download. Everything listed above is part of this plugin and works without it. * 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 Part of the **Forge Suite** — bundle includes Lang Forge, Rank Forge, Form Forge. ### External services Every outbound request this plugin makes is listed below. Activating it, and opening its screens, contacts nobody. * **oEmbed field.** An oEmbed field asks WordPress to fetch the embed from the provider of the URL an editor enters, exactly as the block editor does: when the field’s value is shown, in the preview under the field in the editor and wherever a theme or a plugin reads the field through the ACF-compatible `get_field()`, WordPress asks that provider’s oEmbed address about the URL. The provider receives the URL and sees the network address of your server. Which provider that is depends on the URL; its terms and its privacy policy are its own. A site that uses no oEmbed field makes no such request. Apart from that this plugin contacts no external service of its own: field groups, values, Local JSON, the ACF importer and REST exposure all run on your site, and there are no analytics, no telemetry and no licensing calls. AI features belong to the separate Field Forge Pro add-on, which describes the services it uses in its own documentation. ## স্ক্ৰীনশ্বট [⌊Field group editor⌉⌊Field group editor⌉[ Field group editor [⌊Repeater field on post edit (Pro)⌉⌊Repeater field on post edit (Pro)⌉[ Repeater field on post edit (Pro) [⌊Migration from ACF⌉⌊Migration from ACF⌉[ Migration from ACF [⌊GraphQL schema preview (Pro)⌉⌊GraphQL schema preview (Pro)⌉[ GraphQL schema preview (Pro) [⌊AI schema generator (Pro)⌉⌊AI schema generator (Pro)⌉[ AI schema generator (Pro) ## ইনষ্টলেশ্যন 1. Upload `fieldforge` to `/wp-content/plugins/`, or install via Plugins Add New. 2. Activate the plugin. 3. Go to **Field Forge Field Groups New Field Group**. 4. Read values in PHP: `$value = get_field('my_field', $post_id);` 5. Or via REST: `GET /wp-json/wp/v2/posts/123/fieldforge` 6. 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. ## পৰ্য্যালোচনা এই প্লাগিনৰ বাবে কোনো পৰ্য্যালোচনা নাই। ## অৱদানকাৰী আৰু বিকাশকাৰীসকল “Field Forge – Custom Fields, Relational Fields & Builder” হৈছে মুক্ত উৎসৰ ছফ্টৱেৰ। এইসকল লোকে এই প্লাগিনত অৱদান আগবঢ়াইছে। অৱদানকাৰীসকল * [ avakodeforge ](https://profiles.wordpress.org/avakodeforge/) “Field Forge – Custom Fields, Relational Fields & Builder” 2টা ভাষাত অনুবাদ কৰা হৈছে। [অনুবাদকসকল](https://translate.wordpress.org/projects/wp-plugins/fieldforge/contributors) ক তেওঁলোকৰ অৱদানৰ বাবে ধন্যবাদ। [আপোনাৰ ভাষাত “Field Forge – Custom Fields, Relational Fields & Builder” অনুবাদ কৰক।](https://translate.wordpress.org/projects/wp-plugins/fieldforge) ### বিকাশৰ প্ৰতি আগ্ৰহী? [ক’ড ব্ৰাউজ কৰক](https://plugins.trac.wordpress.org/browser/fieldforge/), [SVN ৰিপজিটৰী](https://plugins.svn.wordpress.org/fieldforge/) চাওক নাইবা [RSS](https://plugins.trac.wordpress.org/log/fieldforge/?limit=100&mode=stop_on_copy&format=rss)- দ্বাৰা [বিকাশৰ পঞ্জী](https://plugins.trac.wordpress.org/log/fieldforge/) ছাবস্ক্ৰাইব কৰক। ## সলনি-পঞ্জী #### 1.0.41 * 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. #### 1.0.40 * 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. #### 1.0.39 * **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. #### 1.0.38 * 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. #### 1.0.37 * No change in this package: the release updated parts that ship only in the edition distributed through avakode.com. #### 1.0.36 * **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. #### 1.0.35 * 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. #### 1.0.34 * 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. #### 1.0.33 * 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. #### 1.0.32 * No change in this package: the release updated parts that ship only in the edition distributed through avakode.com. #### 1.0.31 * Smaller package and one less admin surface: the SDK’s own menu, opt-in screen and promotional notices are gone. #### 1.0.30 * No change in this package: the release updated parts that ship only in the edition distributed through avakode.com. #### 1.0.29 * No change in this package: the release updated parts that ship only in the edition distributed through avakode.com. #### 1.0.28 * 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. #### 1.0.27 * 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. #### 1.0.26 * 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. #### 1.0.25 * 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. #### 1.0.24 * 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. #### 1.0.23 * 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. #### 1.0.22 * 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. #### 1.0.21 * 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. #### 1.0.17 * 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). #### 1.0.16 * 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). #### 1.0.14 * 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. #### 1.0.0 * Initial release. ## মেটা * **1.0.41** সংস্কৰণ * **24 ঘণ্টা আগত** শেষবাৰ আপডে’ট হৈছিল * সক্ৰিয় ইনষ্টলেশ্যন **10+** * WordPress-ৰ সংস্কৰণ ** 6.5 বা তাতকৈ ওপৰৰ ** * ইমানলৈকে পৰীক্ষা কৰা হৈছে **7.1.3** * PHP-ৰ সংস্কৰণ ** 7.4 বা তাতকৈ ওপৰৰ ** * ভাষাবোৰ * [English (US)](https://wordpress.org/plugins/fieldforge/), [Spanish (Chile)](https://cl.wordpress.org/plugins/fieldforge/) আৰু [Spanish (Spain)](https://es.wordpress.org/plugins/fieldforge/). * [আপোনাৰ ভাষাত অনুবাদ কৰক](https://translate.wordpress.org/projects/wp-plugins/fieldforge) * [builder](https://as.wordpress.org/plugins/tags/builder/)[custom fields](https://as.wordpress.org/plugins/tags/custom-fields/) [custom table](https://as.wordpress.org/plugins/tags/custom-table/)[meta fields](https://as.wordpress.org/plugins/tags/meta-fields/) [relational fields](https://as.wordpress.org/plugins/tags/relational-fields/) * টেগবোৰ * [উচ্চখাপৰ ভিউ](https://as.wordpress.org/plugins/fieldforge/advanced/) ## ৰে’টিংবোৰ এতিয়ালৈ কোনো পৰ্য্যালোচনা দাখিল কৰা হোৱা নাই। [Your review](https://wordpress.org/support/plugin/fieldforge/reviews/#new-post) [সকলো পৰ্য্যালোচনা চাওক](https://wordpress.org/support/plugin/fieldforge/reviews/) ## অৱদানকাৰীসকল * [ avakodeforge ](https://profiles.wordpress.org/avakodeforge/) ## সাহায্য কিবা ক’বলগীয়া আছে? সহায় লাগে? [সাহায্যৰ ফ’ৰাম চাওক](https://wordpress.org/support/plugin/fieldforge/) ## দান কৰক আপুনি এই প্লাগিনৰ উন্নতিৰ প্ৰতি সাহায্য আগবঢ়াব বিচাৰেনে? [ এই প্লাগিনক অনুদান দিয়ক ](https://avakode.com)