Toolset Types 3.4.17 – Bugfix Release
We just released Toolset Types 3.4.17. This update includes fixes for various issues as well as a performance improvement.

Our team is continuing to make sure Toolset is stable and performs well on your sites. In addition to the Types 3.4.17 release, you can expect other updates coming soon for Blocks, Views, and other Toolset plugins.
What’s New in Types 3.4.17
Fixes
- Addressed various issues with the WYSIWYG field by implementing a much more stable fix for the race condition caused by a WordPress bug: https://core.trac.wordpress.org/ticket/53644.
- Fixed a compatibility issue with the Uncanny Automator plugin that was breaking its TinyMCE inputs.
- Prevented a fatal error in the background while sending posts with Repeatable Field Group items to translation.
- Ensured that custom post fields with the Copy and Copy once translation settings are correctly pre-populated on a New Post page.
- Fixed image editing issues related to PHP 8 compatibility.
- Prevented a PHP warning (or error in PHP8) when multiple values are passed to
meta_keyin WP_Query arguments.
Performance
- Added a minimum length to autocomplete on some Toolset listing pages in the WordPress admin.
How to Update to Toolset Types 3.4.17
We are rolling this release out gradually, so not everyone will see it right away. If you want to update before it’s available to you, you can manually check for the update. To do this, go to Plugins → Add New and click the Commercial tab. Then, click Check for updates to see the available update.
Share Your Feedback
If you have any questions or comments, please let us know in the comments below, and we’ll reply!

Would be great if this update fixes my memory issues I’m having with authors in combination with toolset access and PHP 8.
I tested Toolset Types 3.4.17 on a test install but I’m having problems. (e.g. it won’t show any existing custom posts when I try to set a relationship). Even if I disable toolset access, the old custom posts don’t appear to connect to an existing custom post.
Should I wait until toolset access is updated and if so, when will it be?
Hi Torsten – Thanks for your comment. We don’t have a release date planned for the next Access update at this time. I consulted our support team about the issue you described, but they would need to investigate further. Please open a support ticket so our team can learn more.
I just noticed that it says “Please enter 3 or more characters”. I just saw that the changelog says, “Added a minimum length for autocomplete on some toolset list pages in the WordPress admin.” I prefer the old way of showing the most recent ones until I started typing. Is there perhaps a setting to bring it back?
Hi Torsten – Sorry for the delay in replying to you! I checked with our developers, and they recommended opening a support ticket about this.
Quite messy after core and module updates.
“Fields and text” block breaks when I try to modify it.
– Fixed after downgrading to WP core v6.0.1 to stop that from breaking and be able to modify it.
“Single field” block lost ability to pull data from custom post types, as these no longer appear in the search form.
– Fixed that using a shortcode block instead
Hi Diyan – Thanks for your comment. If you haven’t already done so, would you mind opening a support ticket about this? That’s the quickest way to escalate these issues, and our support team will be able to investigate them further.
Ya the fields and text blocks being broken with the latest Version of WP needs to be fixed quickly. I would have expected a major feature to be tested/patched prior to public release of this. It’s really showing toolsets true intentions of the future of toolset and it’s scary for us with sites out there in the wild!
Hi Nicholas – Thanks for your comment. Our developers are preparing a fix right away for the next release. You can monitor this erratum for updates: https://toolset.com/errata/fields-and-text-block-broken-with-wordpress-6-1-update/