Toolset Types 3.6.0

Compatibility

• Updated the Installer component to ensure compatibility with WordPress 5.3.
• Adjusted styling to match the new WordPress 5.3 styling.
• When saving an image field with a value that corresponds to an attachment ID, ensure that the URL corresponds to the original image version and not to a scaled-down one, which could lead to performance issues on the front-end.

Translations

• Updated translation files for all supported languages.

Fixes

• Fixed a cosmetic issue with checkboxes labels on the Add/Edit term page.
• After saving a post in the Block Editor, show a notice about changed display conditions for field groups only if they’ve actually changed.
• On the Toolset Dashboard page, don’t render links to edit taxonomies that are registered by a third party.
• Fixed the way URL from a file-like custom field is translated into attachment ID when generating a preview. Also, made sure image previews don’t escape their boundaries even if a full-size image is used.
• Don’t show a file upload button for custom fields when the user doesn’t have file upload permissions. Display a subtle note about upload permissions when editing file-like custom fields.
• Fixed a cosmetic issue with a tooltip when using a copy of a field value from the original language post.

Fix a compatibility issue with Contact Form 7 that produces a notice in PHP 5.6.
Fix an error with “undefined function get_current_screen()” during Types import.
Fixed: Compatibility issue with the embedded version of Twig library.
Fix a link in the REST API Settings decription.
Hide the Views column from Toolset Dashboard if Toolset Blocks is active.
Fix a proper attachment ID detection when a custom upload path is used (the result of this issue was that images didn’t have proper alt and title attributes in some cases).
Fixed: Field display conditions not working properly in repeatable field groups.
Avoid overescaping option labels of custom fields (checkboxes, radio) if they contain an apostrophe.

Performance and user interface updates for Repeatable Field Groups. This makes them more scalable and usable in more complex scenarios (larger amounts of data, multiple levels of nesting, multiple WYSIWYG editors, etc.).