Field Forge – Custom Fields, Relational Fields & Builder

Registro de cambios

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.