FieldForge

更新日志

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 load_plugin_textdomain() 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: 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).

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.