Version 1.2.6 solves a problem with dynamic field initialization in Fieldmanager metaboxes when the new block editor, Gutenberg, is active. If available, it utilizes the new wp.domReady helper to load Fieldmanager’s JavaScript so that it doesn’t attempt to initialize dynamic fields before they have fully loaded. Additionally, it uses the version constant to bust the asset cache on platforms like WordPress VIP, so you can be certain that you are always getting the correct JavaScript for the version of Fieldmanager that you are using.

This release was thoroughly tested on several high traffic sites over the past few months in a beta stage without demonstrating any adverse effects. However, if you discover any problems while using the new version, please report them using our issues page on GitHub.

This release is the culmination of 1,070 commits, by 24 people, spread out over 3.5 years. Thanks and shout-outs to all those who have contributed to Fieldmanager to make this release possible (in order of commits):

mboynes, bcampeau, netaustin, danielbachhuber, nschoenholtz, dlh01, xmattus, stevenslack, jitendraharpalani58, amaschas, joshkadis, firejdl, goldenapples, montchr, mattheu, joshbetz, ericandrewlewis, aaronjorbin, srtfisher, enrico-sorcinelli, alexisbellido, dmachat, zgreen, and matthewspencer.

On to 1.1!

• User forms (#157)
• Network settings submenus (#120)
• Gallery field (#174)
• Customizer context (#399)
• REST API integration (#404, #407)
• UI Update (#468)
• Improve adherence to coding standards (#271) — we need a lot of help with this one!

If there is anything else you’d like to see in this release, submit an issue and let us know about it!

If you find any bugs, please file an issue on GitHub.