

Bug fix: Support cases where there are multiple WP_Editor instances on a page, and make sure that the shortcode being edited is sent to the correct page.Bug fix: Fix some issues where the media modal state was not reset properly if a shortcode was closed without saving.


Security: Use nonce validation in ajax render shortcode callback to protect against CSRF.(This option defaults to off and should not affect existing fields.) Enhancement: add an optional "allow clear" field attribute to be passed to select2 fields (post, user, or term select) so that multi-select fields can be cleared with a single click.Bug fix: Fix a bug where the "Select Files" button in the media controller became unresponsive after a post element has been inserted.Bug fix: Fix a javascript error which would cause the Insert Post Element modal to be blank if any shortcode contains a select field with no visible options and no default set.Block editor compatibility: prevent templates from being output before the document head, which forced the browser into quirksmode, breaking some CSS styles in the block editor.
#Shortcake ui iconbox registration#
If you were using this to support editing inner content, you'll need to change your UI registration to use inner_content. We've removed the compatibility shim for the magical content attribute. You should register a placeholder for your field using the meta argument. We've removed the compatibility shim for the placeholder attribute argument. Add new shortcodes to your post through "Add Media". And add a user-friendly UI to edit shortcode content and attributes.Ĥ. But with Shortcake, TinyMCE will render the shortcode in a TinyMCE view.ģ. Without Shortcake, shortcodes have a minimal UI.Ģ.
#Shortcake ui iconbox update#
To update the core WordPress files used by the Jasmine test suite, run grunt updateJasmineCoreScripts -abspath="/path/to/wordpress-install". Jasmine tests can be run using grunt jasmine and are also run as part of the grunt scripts task. We have test coverage for PHP using PHPunit, and JavaScript using Jasmine. If you find that you're experiencing conflicts with these plugins, you can set a flag to load select2 in a distinct namespace by defining the constant SELECT2_NOCONFLICT in your wp-config.php (or anywhere that's defined before the 'init' hook.) (Popular plugins with known conflicts include WooCommerce and Advanced Custom Fields Pro, among others.) This causes a known conflict with plugins that enqueue older versions of Select2. In version 0.7.0, we updated to the most recent branch of the Select2 library, which provides the enhanced select fields in these field types. After upgrading to Shortcake 0.7.x, some of the shortcode UI fields (post select, user select, etc) don't work as expected. Shortcake doesn't support custom key => value pairs as shortcode attributes because it isn't a great user experience. Frequently Asked Questions How do I register UI for arbitrary key/value pairs as shortcode attributes? Action hooks can be used to dynamically show or hide a field based on the value of another, or to implement custom validation rules. New in 0.4.0 is the ability to attach javascript functions to event attribute updates. Once you've done so, you'll need to register the UI for your code. Shortcake can be installed like any other WordPress plugin. To report bugs or feature requests, please use Github issues. For inspiration, check out examples of Shortcake in the wild. Once you've installed the plugin, you'll need to register UI for your shortcodes. Used alongside add_shortcode, Shortcake supplies a user-friendly interface for adding a shortcode to a post, and viewing and editing it from within the content editor. Shortcake makes using WordPress shortcodes a piece of cake. Contributors: fusionengineering, mattheu, danielbachhuber, zebulonj, goldenapples, jitendraharpalani, sanchothefat, bfintal, davisshaver, garyj, mte90, fredserva, khromov, bronsonquick, dashaluna, mehigh, sc0ttkclark, kraftner, pravdomil
