We just released an update for Toolset which focuses on compatibility with WordPress 5.0 and Gutenberg. You will find Gutenberg blocks, a better workflow and many usability improvements.
Last week, we shared our vision of how we see Toolset and Gutenberg editor working together. Now, we take a big first step in making sure Toolset plugins are ready for WordPress 5.0 and the new Gutenberg editor, even before the final release.
Custom Toolset blocks
You can now use four custom Toolset blocks in the Gutenberg editor:
- View block
- Content Template block
- Form block
- Map block
These blocks allow you to insert the related Toolset element and tweak its options using the main sidebar.
Here’s a short video that demonstrates the new Toolset blocks.
Toolset buttons in native Gutenberg blocks
We added our Toolset buttons to Gutenberg’s two main, native blocks: Classic editor and Paragraph.
This means you can insert all dynamic Toolset shortcodes just as in the classic WordPress editor.
Other important features
There are other important features in this release:
|You can use Gutenberg to design Content Templates and the View’s Loop Output.|
|Post relationships and repeatable field groups work properly:|
|There is a dedicated option when editing a custom post type, to turn Gutenberg on or off for that post type. This way, you can choose if you’re using Gutenberg or the classic editor for each content type.|
|All taxonomies are now automatically displayed in the Gutenberg editor.|
|Existing custom fields work normally in the Gutenberg editor.|
Bugfixes and Other Improvements
This release also fixes a lot of bugs that are not related to Gutenberg. Here is a selection of the most important ones.
- Fixed an issue with Beaver Builder when used as a Content Template editor, inside a View Loop that updated its results using AJAX.
- Fixed an issue with the Toolset Elementor widgets where the “Upgrade to PRO” encouragement message lost its styling on the latest version of the editor.
- Fixed an issue between Content Templates and WPML where the modified extra CSS and JS weren’t copied to the translations of a Content Template when its default language was modified.
- Fixed an issue with the “wpv-post-excerpt” shortcode which was creating empty paragraphs when it was used with “noautop” format inside a Content Template.
- Fixed an issue where “wpv-post-featured-image” shortcode sometimes used GUID as image URL.
- Added the ability to select multiple media files at once on repeating media fields.
- Added a new option to automatically delete or keep intermediary posts of a relationship when a connection between posts is deleted.
- Added pagination for the input field of the related content metabox.
- Added time (if available) in the Date field when it is displayed as a column in the post listing page.
- Improved intermediary field group page that now has separate buttons for saving and returning to relationship.
- Improved post field group page where settings will now stay open if no field is added to the group.
- Improved built-in post type labels when they are edited with Types.
We are now testing everything with WordPress 5.0 Release Candidate which was just published. We will be closely watching for any important changes and keep trying to get the WordPress Core team to resolve some open issues we are waiting for.
Give it a try!
While we can’t recommend running WordPress 5.0 beta or release candidates on live sites, this is a good time to start testing Gutenberg with your existing Toolset-based sites – in a test environment, of course.
Simply head to your account’s Downloads page and download the latest versions of our plugins.