Contributors: dlh, jamesburke, alleyinteractive
Requires at least: 4.5
Tested up to: 4.7
Stable tag: 0.4.0
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
A Fieldmanager Beta plugin for the Customize Context.
This is a proposed Customize context for Fieldmanager. You can install the plugin alongside a stable Fieldmanager release to help test and refine the context.
The official Pull Request for this context is on GitHub.
-
Install and activate Fieldmanager.
-
Install and activate this plugin.
-
Use the
fm_beta_customize
context action to instantiate your fields. For example:add_action( 'fm_beta_customize', function () { $fm = new Fieldmanager_TextField( 'My Field', [ 'name' => 'foo' ] ); fm_beta_customize_add_to_customizer( 'My Section', $fm ); } );
For more code examples, browse php/demos/class-fieldmanager-beta-customize-demo.php
. To see the demos in action in the Customizer, place add_action( 'fm_beta_customize', 'fm_beta_customize_demo' )
in your plugin or theme.
- Added: PHP and JavaScript tests.
- Added: Demo a field with selective-refresh support.
- Changed: Use better TinyMCE events for tracking
Fieldmanager_RichTextArea
changes. - Changed: Require at least WordPress 4.5.
- Fixed: Fix a case where invisible Customizer sections could be created.
- Fixed: Track the changes to instances of repeatable RichTextAreas and Colorpickers added after loading the Customizer.
- Changed:
Fieldmanager_RichTextArea
is now supported natively; usingFieldmanager_Beta_Customize_RichTextArea
is no longer required. - Changed: Move remaining scripts that overrode Fieldmanager core assets into separate files.
- Fixed: Fix invisible TinyMCE popups.
- Deprecated:
Fieldmanager_Beta_Customize_RichTextArea
, per above.
- Fix JavaScript errors.
- Move CSS, and autocomplete and datepicker scripts, into separate files, rather than overriding those assets in Fieldmanager core.
- Rename the Customize context action to 'fm_beta_customize' for improved future compatibility with Fieldmanager.
- Initial release.