v1.6.1

What's Changed

• Issue-863: PHP Deprecated: htmlspecialchars(): Passing null to parameter #1 ($string) of type string is deprecated by @anubisthejackle in #865
• Issue-864: Resolve PHP Deprecations by @anubisthejackle in #866
• Issue-867: Update class constructor docblocks to support specifying an array or a string for $label by @nikkifurls in #869

New Contributors

• @anubisthejackle made their first contribution in #865
• @nikkifurls made their first contribution in #869

Full Changelog: 1.6.0...v1.6.1

1.6.0

Changelog

Added

• fm_context_construct action in Fieldmanager_Context. Props @mogmarsh.

Fixed

• Array-to-string conversion in Fieldmanager_Autocomplete. Props @mslinnea.
• Compatibility with composer/installers 2.0. Props @crazyjaco.

1.5.0

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.

Changelog

Fixed

• Protect against side effect term updates #832

1.4.1

1.4.1 is a bugfix release.

Changelog

Fixed

• Fixes performance regression in fm_renumber() (#828).

1.4.0

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.

Changelog

Added

• Fieldmanager_Content_Plaintext, Fieldmanager_Content_Markup, and Fieldmanager_Content_Markdown classes for displaying static content. These extend the new Fieldmanager_Content abstract class (#781).

Changed

• UI overhaul for all field types and meta boxes, including more spacing between fields, more information about selected media files, and improvements for repeatable, sortable, and tabbed interfaces (#468).
• Minimum supported versions of PHP and WordPress are now 7.4 and 5.8, respectively (#814).

Fixed

• Fix various issues with fields displayed in the block editor (#796, #815).
• Ensure that TinyMCE is initialized for Fieldmanager_RichTextArea fields inside meta boxes that are collapsed on page load (#628).
• Don't lose selected Fieldmanager_Radios value when sorting (#658).
• Consistently apply fm_presave_alter_values filter in Fieldmanager_Options subclasses (#568).
• Fix warning from term datasource when saving in submenu context (#791).
• Prevent collisions across different extensions of Fieldmanager_Datasource when generating Ajax action names (#794).
• Refresh nonces with heartbeat responses to prevent data loss (#677).
• Fix inability to save empty multiselect and checkboxes fields when 'serialize_data' => false (#811).
• Docs fixes (#784).

Deprecated

• Fieldmanager_Grid (#795).

Release credits

@benjmyers, @discoinfiltrator, @isGabe, @jameswburke, @joemcgill, @jomurgel, @kevinfodness, @kjbenk, @mboynes, @mogmarsh, @montchr, @mslinnea, @mviggiano, @pattiereaves, @renatonascalves, @stevenslack, @willgladstone

1.4.0 RC1

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.

1.4.0 Beta 1

Fieldmanager 1.4 Beta 1 is now available for testing. The highlights of version 1.4 include:

• Refreshed UI: Lots of subtle and not-so-subtle changes that add up to a greatly improved user experience.
• New field types for static content: Use Fieldmanager_Content_Plaintext, Fieldmanager_Content_Markup, or Fieldmanager_Content_Markdown to display arbitrary content, like a "Help" tab in a group.
• Improved Gutenberg compatibility: Fixes for date fields, autocomplete fields, and various other issues in the block editor.

Along with more bug fixes and enhancements.

Please test (in a non-production environment) and report any issues or feedback in GitHub.

1.3.1

1.3.1 is a bugfix release.

Changes

• Fixes field reordering bug in the block editor (#815, #820).

1.3.0

• Adds a new context for Menu Item.

1.2.6

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.