Toolset 1.6 – WordPress 5.8 Compatibility and Bugfixes
This joint release of Toolset plugins ensures full compatibility with WordPress 5.8. It also includes fixes more than 150 bugs and usability issues.
WordPress 5.8 Compatibility
WordPress 5.8 is out and Toolset is ready for it. The major new feature in WP 5.8 is the new Query Loop block. This block offers some of the features that Views have been offering for several years. It doesn’t yet include support for custom fields, taxonomy, etc.
The major difference between the WordPress Query Loop block and Toolset’s Views and Archives is in how the two designs treat dynamic sources.
The WordPress team decided to implement dynamic sources as individual blocks. There’s the Post Title block, Post Content block, etc.
In Toolset, we’ve chosen a different approach. Toolset doesn’t have dedicated blocks for different types of fields. Instead, it allows you to display fields inside any existing block. This way, you can create a button that displays a label from one field and links to the URL coming from another field. Toolset also offers Inline Fields, which allow you to combine values from fields inside any text.
We think that our approach is way more flexible, but we’re a little biased…
This release of Toolset also includes a huge number (150) of stability improvements:
- Blocks: better management of multiple fast interactions on frontend forms set to update results when visitors make any form change.
- Blocks: fixed a problem with srcset attribute generation for SVG images.
- Blocks: better management of combined sorting and pagination frontend controls.
- Blocks: inline fields using checkboxes should produce labels and not raw stored values.
- Blocks: fixed pause on hover on automatic AJAX pagination.
- Blocks: fixed the ability to search on frontend by title only or title plus content.
- Types: fixed a problem with default field values being set when editing posts.
- Types: fixed a problem with field groups conditions based on taxonomies on multilingual old sites.
- Forms: fixed a problem with notifications set to be sent when a custom field changes its value.
- Forms: fixed a problem when submitting forms with field names already used for post types or taxonomies, or reserved by WordPress.
- Forms: fixed a problem with WPML and post expiration notifications not being sent in the right language.
- Forms: fixed a problem with selectors on forms to create related posts based on an URL parameter losing the value after the form is submitted.
- Forms: fixed a problem with forms to create related posts when the related item selection gets its value from an URL parameter and the field has restrictions by author.
- Forms: fixed a problem when creating items on a Repeatable Fields Group as the parent post was not being required.
- Forms: fixed saving single line fields containing an apostrophe.
- Forms: fixed rendering forms using the PHP function API if they are submitted without page reload.
- Maps: fixed a problem with missing cached addresses on sites with a large number of maps and markers.
- Maps: fixed a default radius of 5km on frontend search filters by distance.
- Access: improved the blocks editor post author selector to include all authors on relevant roles that can publish posts of the current post type.
You can find the full changelogs here:
- Toolset Blocks 1.6
- Toolset Forms 2.6.10
- Toolset Types 3.4.11
- Toolset Maps 2.0.9
- Toolset WooCommerce Blocks 3.1.1
- Toolset Access 2.8.12
- Toolset Views 3.6
- Toolset Framework Installer 3.1.16
Download and Update
As we send out the update notifications in batches not everyone will see the update notice at once.
To get this update now, in the WordPress admin go to Plugins → Add New and click the Commercial tab. There, click the Check for updates button in the Toolset section.
What do you think of the new features in WordPress 5.8 when compared to Toolset? Leave your comments and we’ll get back to you.