Toolset Blocks 1.3.2 and Types 3.4.2 – Better Performance and Stability


October 20, 2020

This release includes Toolset Blocks 1.3.2, Toolset Types 3.4.2, Toolset Forms 2.6.2, and Toolset WooCommerce Blocks 2.9.2 plugins.

Faster editing and lighter server load

We’ve optimized the communication between our code inside the Gutenberg editor and the server. Now, Toolset will call the server much less frequently in order to get dynamic fields and Views. This will make the editor feel a lot faster and put much less load on the server when you’re editing content.

Other Improvements and Fixes

Here are some other important improvements and fixes in this release:

  • WooCommerce Blocks compatibility with the Woodmart Theme
  • Better compatibility with PHP 7.4
  • Fixed infinite scrolling on archives loading results in the wrong place
  • Fixed the mechanism to use a View as a source of options for a Forms generic field

You can check the full changelogs here:


Any thoughts on this release? Leave your comments and we’ll get back to you.


Comments 4 Responses

    • Hi, Darryl! I don’t understand the question. Toolset Access works fine with Toolset Blocks. If you need to display content based on user roles, you can do that with the Toolset Conditional block. Is there any special Access feature that you need in the Block Editor that the Conditional block doesn’t provide? What are you trying to build?

      • In Access I can test against the “Guest” role for people not logged in, then display a way for them to login.

        In the Toolset Blocks I can test to see if someone ISN’T any of the existing roles but that falls apart if/when a new role is added.

        • OK, here’s the thing. For what you’re describing you should use Access itself directly, without the need to involve the Conditional block.

          In short, you need to create 2 templates:
          – One template that displays content for the “Guest” (not logged-in) users. This template displays the log-in form.
          – One template that displays full content for the logged-in users.

          Then, you go to Toolset → Access Control and set up the access to the post type so that “Guest” users see the template with the login form, while the logged-in users see the template with full content.

          All of this is explained in our documentation, here:

          Besides this, I created a feature request for the possibility to use Conditional block to check against the “Guest” users and the request was granted. I don’t have an ETA for this, but it is now on our roadmap for one of the upcoming releases.