NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist
Packagist, #3611 most downloaded on Packagist
A library to build forms and admin screens for WordPress
Latest stable
v1.6.3
Last release 3 months ago
12 Aug 2026
Release timing varies
gaps range from 4 weeks to 2.0 years
Nearly every release is documented
notes for 17 of 17 stable releases
Nothing withdrawn
no release was ever pulled
11 years old
21 releases · first in 2016
Drag across the ruler to compare, or tap a release to open it.
Fix local times saved across DST change by @mboynes and @vancoder in https://github.com/alleyinteractive/wordpress-fieldmanager/pull/761
Full Changelog: https://github.com/alleyinteractive/wordpress-fieldmanager/compare/v1.6.2...v1.6.3
Fix typos by @szepeviktor in https://github.com/alleyinteractive/wordpress-fieldmanager/pull/871
Full Changelog: https://github.com/alleyinteractive/wordpress-fieldmanager/compare/v1.6.1...v1.6.2
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Issue-863: PHP Deprecated: htmlspecialchars(): Passing null to parameter #1 ($string) of type string is deprecated by @anubisthejackle in https://gith…
array or a string for $label by @nikkifurls in https://github.com/alleyinteractive/wordpress-fieldmanager/pull/869Full Changelog: https://github.com/alleyinteractive/wordpress-fieldmanager/compare/1.6.0...v1.6.1
fm_context_construct action in Fieldmanager_Context. Props @mogmarsh.
fm_context_construct action in Fieldmanager_Context. Props @mogmarsh.Fieldmanager_Autocomplete. Props @mslinnea.1.5.0 resolves an edge-case bug in the Term Context that could lead to unexpected data writes or even data corruption. Because this change was not inc
1.5.0 resolves an edge-case bug in the Term Context that could lead to unexpected data writes or even data corruption. Because this change was not inconsequential, we opted to ship a minor release as opposed to a patch release.
The Term Context bug can be read about in depth in #831 and #832; props to @johnbillion for reporting it. TL;DR: if a term is being added or edited and has fields from the Term Context, and during the "save" POST request, there is a side effect where another plugin or theme creates or updates an additional term, then the field data would be written to that term as well.
Of note, this bugfix additionally spawned https://core.trac.wordpress.org/ticket/55441.
Fixes performance regression in fm_renumber() (#828).
1.4.1 is a bugfix release.
fm_renumber() (#828).This is the first release candidate for Fieldmanager 1.4. It is unchanged from Beta 1 and, pending bug reports, will be published as the official rele
This is the first release candidate for Fieldmanager 1.4. It is unchanged from Beta 1 and, pending bug reports, will be published as the official release on or around Feb. 8, 2022.
Please test (in a non-production environment) and report any issues or feedback in GitHub.
Fieldmanager 1.4 Beta 1 is now available for testing. The highlights of version 1.4 include:
Fieldmanager_Content_Plaintext, Fieldmanager_Content_Markup, or Fieldmanager_Content_Markdown to display arbitrary content, like a "Help" tab in a group.Along with more bug fixes and enhancements.
Please test (in a non-production environment) and report any issues or feedback in GitHub.
Fieldmanager 1.4 includes a refreshed UI for all field types, new fields for displaying static content or HTML, and improved compatibility with the block editor.
Fieldmanager_Content_Plaintext, Fieldmanager_Content_Markup, and Fieldmanager_Content_Markdown classes for displaying static content. These extend the new Fieldmanager_Content abstract class (#781).Fieldmanager_RichTextArea fields inside meta boxes that are collapsed on page load (#628).Fieldmanager_Radios value when sorting (#658).fm_presave_alter_values filter in Fieldmanager_Options subclasses (#568).Fieldmanager_Datasource when generating Ajax action names (#794).'serialize_data' => false (#811).Fieldmanager_Grid (#795).@benjmyers, @discoinfiltrator, @isGabe, @jameswburke, @joemcgill, @jomurgel, @kevinfodness, @kjbenk, @mboynes, @mogmarsh, @montchr, @mslinnea, @mviggiano, @pattiereaves, @renatonascalves, @stevenslack, @willgladstone
This is the first release candidate for Fieldmanager 1.4. It is unchanged from Beta 1 and, pending bug reports, will be published as the official rele
This is the first release candidate for Fieldmanager 1.4. It is unchanged from Beta 1 and, pending bug reports, will be published as the official release on or around Feb. 8, 2022.
Please test (in a non-production environment) and report any issues or feedback in GitHub.
Fieldmanager 1.4 Beta 1 is now available for testing. The highlights of version 1.4 include:
Fieldmanager 1.4 Beta 1 is now available for testing. The highlights of version 1.4 include:
Fieldmanager_Content_Plaintext, Fieldmanager_Content_Markup, or Fieldmanager_Content_Markdown to display arbitrary content, like a "Help" tab in a group.Along with more bug fixes and enhancements.
Please test (in a non-production environment) and report any issues or feedback in GitHub.
Fixes field reordering bug in the block editor (#815, #820).
1.3.1 is a bugfix release.
Nothing published for this version
Adds a new context for Menu Item.
Fixes issues with Fieldmanager fields, which require JavaScript hooks, not initializing properly when Gutenberg is active. wp.domReady fires later tha
Fixes issues with Fieldmanager fields, which require JavaScript hooks, not initializing properly when Gutenberg is active. wp.domReady fires later than jQuery's document.ready, so this, combined with moving most FM scripts to the footer, resolves race conditions that prevent initialization of dynamic fields across the board in Fieldmanager.
Additionally, uses FM_VERSION to set version numbers for Fieldmanager JS and CSS to ensure cache busting when shipping a new version of Fieldmanager to aggressively cached sites, such as VIP Go. Accordingly, bumps the version to 1.2.6.
Finally, moves script load for most FM scripts to the footer, which is required for proper initialization of fields in a Gutenberg context, and is generally a best practice.
1.2.4 is a bug fix and security release.
1.2.4 is a bug fix and security release.
@ravatparmar, @dlh01, @mslinnea, @mboynes
Fixed: PHP warning when attempting to set a validation error message (#689).
1.2.3 is a bug fix release.
@terrarum
Fixed: Ensure Fieldmanager_Datasource_Term loads terms by their saved term_order (#699).
1.2.2 is a bug fix release.
Fieldmanager_Datasource_Term loads terms by their saved term_order (#699).Fix bug where checkboxes used for display_if may not initialize properly
1.2.1 is a bug fix release.
display_if may not initialize properly (#678)This release has a few potentially (albeit _very_ low-risk) breaking changes to be aware of:
Fieldmanager version 1.2.0 is a janitorial release. Coding standards updates and bug fixes aplenty!
This release has a few potentially (albeit very low-risk) breaking changes to be aware of:
Fieldmanager_Draggable_Post and Fieldmanager_Context_Page are now deprecated. Flagging them as deprecated doesn't technically make for a breaking change, but using them will now throw a warning. See #653.Fieldmanager_Colorpicker::sanitize_hex_color() was removed in favor of core's sanitize_hex_color(). See #669, #492..DS_Store file (#572)this in fm_remove() (#577)dev branch to Travis CI tests (#465)get_terms() arguments (#541)0 (#664)See the full diff for additional details.
@kjbenk, @dlh01, @mboynes, @mslinnea, @pjpak, @mjangda, @szepeviktor, @david-binda, @joshkadis, @s3rgiosan, @kkoppenhaver, @srtfisher, @ethitter
Breaking change: Fix argument order for optgroup key=>val pairs
Fieldmanager_Media (#545)See the full diff for additional details.
@dlh01, @mboynes, @kjbenk, @scottnelle
This is the official 1.0 release of Fieldmanager. This release is the culmination of 1,070 commits, by 24 people, spread out over 3.5 years. Nothing s
This is the official 1.0 release of Fieldmanager. This release is the culmination of 1,070 commits, by 24 people, spread out over 3.5 years. Nothing significant changed since the 1.0.0-rc release candidate.
Read more about Fieldmanager at http://fieldmanager.org/.
This is a release candidate for 1.0.0. Pending bug reports, we'd like to publish this as the official 1.0 release this week.
This is a release candidate for 1.0.0. Pending bug reports, we'd like to publish this as the official 1.0 release this week.
Fieldmanager_Colorpicker (#412)See the full diff, or the PR list for a deeper look at the goodness.
@mboynes, @danielbachhuber, @dlh01, @nschoenholtz, @stevenslack, @joshkadis, @enrico-sorcinelli, @goldenapples, @xmattus, @aaronjorbin
One column per quarter.