Toolset Types

• Enhancement: extend the labels offered for Custom Post Types and Custom Taxonomies to cover most of the WordPress API.
• Enhancement: include filters to modify the labels of the items offered when creating a relationship association.
• Compatibility: translate Custom Post Types, Custom Taxonomies, Fields Groups, and Relationships using the WPML Translation Management dashboard.
• Compatibility: use the right translations for labels on Custom Post Types, Custom Taxonomies, Fields Groups, and Relationships, when changing the admin language with WPML.
• Fix: do not produce an error when displaying image fields for images stored in non-standard locations.
• Fix: avoid problems when editing Custom Post Types or Custom Taxonomies labels with a different number of placeholders than expected.
• Fix: remove a JavaScript dependency no longer included with WordPress.
• Fix: add some security checks when automatically generating WooCommerce field groups.

• Fix: fields validation when changing the field type.
• Fix: do not include assets provided by WordPress.
• Usability: improve the example when creating one-to-one relationships.

• Fix: properly load the forms library.

• New: two new filters types_relationship_connect_existing_options and types_relationship_connect_existing_options[{relationship_slug}][{related_post_type}] to shortcircuit the query to populate the options when setting relationships with existing post types.
• Fix: avoid errors on PHP 8+ when processing malformed date field values.

• Compatibility: test against WordPress 6.3.
• Fix: custom validation options missing for URL, date, and numeric fields on PHP 8.x.

• Fix: typo in relationships creation wizard triggers a console error.
• Fix: get_page_by_title is deprecated in WordPress 6.2.
• Fix: warning on PHP8 when using the relationships migration tool if WPML is not active.
• Fix: prevent a PHP warning (or error in PHP8) when multiple values are passed to ‘meta_key’ in WP_Query arguments.

• Fix: remove files after failing to import.
• Fix: warning about private final methods on PHP 8.

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_key in WP_Query arguments.

Performance

• Added a minimum length to autocomplete on some Toolset listing pages in the WordPress admin.

• Compatibility with PHP8.
• Fixed a problem when WYSIWYG fields were not properly saved on the classic editor.
• Fixed a problem when WYSIWYG fields were not properly initialized on the blocks editor.

• Fixed custom field validation for post types without post content.
• Fixed the styling of the horizontal view of Repeatable Field Groups in case there are many fields to display.
• Prevented possible database integrity issues when creating new post relationships in high-traffic environments.
• Fixed a compatibility issue with the most recent versions of WordPress that was breaking several block editor-specific adjustments in Types.
• Made sure that attachment metadata is always fetched in the correct language when using the types shortcode.
• Prevented an error when receiving a completed translation job from the Advanced Translation Editor when repeatable custom fields are involved.

Fixes

• Fixed a regression that was causing issues with saving WYSIWYG fields.

• Fixed a problem when clearing values for fields hidden due to conditionals.

• Fixed conditional display of custom fields.

• When editing connected posts in the Related Content metabox via Quick Edit, the notice about editing connected post’s fields now becomes much less aggressive. Once dismissed permanently, the choice will be remembered for all custom post types and relationships on a per-user basis.
• Improved color picker fields by having a preview of the selected color.
• Better columns in admin listing pages for custom post types and custom taxonomies.
• Addressed a usability issue with trashed posts in the Related Content metabox. Until now, a trashed parent post of a one-to-many relationship meant that when editing the child post, it is not being displayed in the GUI but it’s not possible to connect another post either. Now, we display trashed posts as well (with a clear distinction), so that it’s possible to either restore or delete them.
• Added the field description to the editor for post reference fields.
• Fixed a rare issue where the “types” shortcode got broken if a custom code was applied to provide custom field options.
• Fixed a minor compatibility issue with the PublishPress Revisions plugin that was producing a PHP warning on its main admin page.
• Fixed the visibility of field groups based on taxonomy terms on old multilingual sites.
• Fixed an issue where display conditions for custom fields were sometimes conflicting with display conditions on custom fields of related posts on the Edit Post page.
• Removed a meaningless placeholder from the Toolset Dashboard table that becomes visible if Views or Blocks is not active.
• Fixed a rare issue where the user’s locale was forced to the current language while using the WPML Translation Editor with Types active.
• Fixed disabling custom field groups and then switching the fields tabs to another domain.
• Fixed broken Screen Options on the Toolset Settings page, where the Items per page setting wasn’t being saved.
• Fixed search on the Custom Code tab of Toolset Settings.
• Fixed an issue that made it possible to edit values of a repeatable custom field that is set to be copied from the original post when editing translatable content.
• Fixed an issue that made it impossible to save an empty value to a field with a defined default value. Until now, even if the user deliberately clears the field and saves it, it was being reset to the default value. From now on, the default value will be applied only for a new element (post, term, user).
• Fixed some glitches in the Toolset Dashboard when the site has disabled post types.
• Improved the New Relationship wizard by blocking it when trying to use a relationship slug that’s already in use.

• When creating or editing a relationship, the “intermediary post type visible in WordPress admin menu” will now affect only the show_in_nav_menus attribute of the post type. Newly created intermediary post types will be public by default (publicly_queryable, show_in_ui will be true, exclude_from_search will be false).
• Fixed an WPML compatibility issue with the order of values of repeatable custom fields not being preserved under specific circumstances: this was happening when a repeatable custom field’s translation setting was “Copy” and existing values of the have been reordered in the original post. In such case, the new order was not reflected on the post translations.
• Make sure that numeric field values of Repeatable Field Group items are translated correctly via WPML Advanced Translation Editor.
• Ensured the maximum size of WPML language flags in various places of the Related Content GUI. This was causing problem only when custom language flag images were used.
• Fix an issue where custom user fields were missing in the REST API output.
• Ensure that intermediary posts are deleted whenever appropriate while using toolset_disconnect_posts(). Until now, they have been always left behind regardless of the relationship configuration.

• Fixed a regression where it became impossible to uncheck several flags on the Edit Post Type page.

Features

• Updated Toolset Dashboard to list the Conditional Content Templates and WordPress Archives for specific taxonomy terms.

Fixes

• Fixed a rare issue that would produce an error when trying to manually connect an intermediary post to a parent or a child post.
• Fixed a JavaScript error on the Associations tab of the Import/Export page.
• Fixed the option for hiding the Related Content metabox for particular post types (on the Edit Post page). Until now, it was being applied only for the user who saved the post type options. Another resaving of each affected post type is necessary in order to apply the setting site-wide.
• Updated a link to Relevanssi documentation that appears in the Types field settings.
• Updated translations for Spanish, French, and German and removed translations for all other languages.
• Addressed an edge-case cache invalidation issue with the public post relationship API.
• Improved translation of Multiline and WYSIWYG fields inside Repeatable Field Groups.
• Fixed editing Repeatable Field Groups when they contain a field of a no-longer-existing type.
• Added a “rel” attribute with the “noopener” value for URL fields displayed as links that open in new tabs.
• Fixed an issue where Types fields content were no longer added to the Yoast SEO Analysis.
• Ensured that the ordering of Repeatable Field Group items is preserved in secondary languages as well.
• Fixed an issue with custom field input validation in Gutenberg.

Fixes

• Addressed an issue with saving empty custom post fields.
• Fixed an issue with sorting admin columns by numeric fields.
• Fixed an issue that caused values of WYSIWYG fields inside Repeatable Field Group to get lost when the group is sorted or collapsed.

Performance improvements

• Additional performance improvements by caching duplicate relationship queries.

• Improved the performance of querying potential associations (when connecting existing posts) for relationships without custom cardinality limits.
• Made the database upgrade introduced in Types 3.4 even safer: Now it is possible to use the site normally during the whole process without any risk of causing data inconsistency. Specifically, deleting an already migrated association between two posts will be propagated to the new database table and the association will stay deleted after the upgrade process completes.
• Fixed a rare issue with database table prefixes ($table_prefix) that contain uppercase letters and MySQL servers that return table names in lowercase. This might have caused problems with the database upgrade after Types 3.4, for example.
• Fixed a rare compatibility issue with the Broadcast plugin that was causing an error when trying to broadcast posts to certain sites due to missing cache invalidation and conflicting post IDs.
• Fixed a Types/WPML interoperability issue that was wrongly deleting post_meta translations for WooCommerce Products.
• Fixed a usability issue with WordPress 5.6, where the Related Content metabox table exceeds the page content width instead of getting a horizontal scroll.
• Fixed an issue that caused WYSIWYG relationship fields to lose their values when connecting existing posts.

• Improved the performance for relationships queries both in backend and frontend.

• Improved the database migration routine for the 3.4.x version.
• Improved compatibility with jQuery 3.5.x as included in WordPress 5.6.
• Improved compatibility with the block editor toolbar changes introduced in WordPress 5.6.
• Improved compatibility with the Twenty Twentyone theme regarding image fields previews.
• Fixed a problem with permissions when trying to quick edit related posts.

• Updated documentation links.
• Performance optimizations for the toolset_relationships WP_Query extension with respect to post type translatability.
• Fixed an issue that caused deleted custom intermediary post types to reappear in the post types list.
• Adding the ability to change the visibility of an intermediary post type from the relationship edit page.
• Fixed an issue that caused WYSIWYG fields in Repeatable Field Groups to become unresponsive after sorting, and radio fields to lose their checked state.
• Fixed the styling of a button in the admin notice for database upgrade introduced in Types 3.4.
• Made the Toolset database upgrade notice collapsible.
• Fixed an issue that caused repetable image fields in a Relationship Related Post section to work only for the first instance.

• Fixed the 3.4 database migration on really large sites.
• Fixed translating some WYSIWYG fields set to copy content form the original post language.
• Fixed a problem when creating a new post type while using PHP 7.4.
• Fixed the formatting for WYSIWYG fields used inside of the blocks editor.

• Fix a compatibility issue with the recent Yoast SEO versions that was breaking the WYSIWYG field editor in Repeatable Field Groups.

• Improved interoperability between WPML and post relationships: Allow for connecting translatable posts without requiring the default language version to exist.
• Fixed a compatibility issue with recent versions of WooCommerce that was producing a TypeError when deleting a post.
• Updated links to documentation.
• The default value for the shortcode format attribute changed from “FIELD_NAME: FIELD_VALUE” to “FIELD_VALUE”.

• Improved compatibility with WordPress 5.5.

Fixes

• Fixed a compatibility issue with plugins that hook into the big_image_size_threshold filter.

Fixes

• Fixed the field validation in block editor that was not working properly if used in combination with conditional field display.
• Fixed an issue that was producing a fatal error when using the toolset_get_relationships() API function and querying by the intermediary post type.
• Fixed an issue with custom WPML language flags being displayed in original size in various places in Types.
• Fixed the taxonomy-based conditional display of post field groups on multilingual sites.
• Fixed a rare PHP 7.4 issue that might have produced a notice in the WordPress admin in some circumstances.
• Fixed an issue where newly created custom fields didn’t have proper default WPML translation settings.
• Added a mechanism to prevent an issue with errors in the WordPress admin when custom post relationship database tables are missing but their existence is assumed. A new filter toolset_m2m_skip_table_existence_check can be used to prevent additional MySQL queries on relevant requests. Additionally, a mechanism to detect and fix orphaned intermediary post types (that don’t have any relationship referring to them) has been implemented on the Troubleshooting page.

Performance

• Significant performance improvement when saving posts with a large number of images in custom fields.
• Added a mechanism to prevent browser from freezing when there are a huge number of fields with conditions in a Repeatable Field Group.

Usability

• Improved wording of the “Delete leftover intermediary posts” routine on the Troubleshooting page to prevent confusion.
• Post editor mode is now copied when a post is translated and in Settings is set to “Per post”.
• Allowing custom slug rewrite rules for post types and taxonomies to contain the same characters as WordPress does.

Enhancements

• We’ve extended the toolset_get_related_posts() arguments by “orderby_role” which allows to specify by which role the ordering should happen (when the “order” argument is used). If the “orderby_role” argument is not present, the behavior doesn’t change and the first of the returned roles is used for ordering.

Fixes

• Removed suppressed deprecation notices coming from the embedded Twig library, which should also bring a minor performance improvement when using Query Monitor in the admin.
• Fixed a recent compatibility issue between the Yoast SEO plugin and Toolset Types that was causing JavaScript errors when using Repeatable Field Groups.
• Updated the Installer component to address issues with fetching plugin upgrades.

Features

• Added an option to include general Toolset settings in the Types export file.

Fixes and compatibility

• Allow using GET parameters in URLs of image fields (useful for hosting images in custom locations, like Amazon S3).
• Update the Installer component to address issues with fetching plugin upgrades.
• Prevented the “wptValidationForms.push is not a function” JavaScript error on the Edit Post page.
• Add a new types_sanitize_field_labels filter to allow disabling the sanitization of custom field labels and field options on sites that rely on having HTML code in those labels. Please note that using this filter is discouraged for new sites.
• Fixed compatibility issues (with plugins like Rank Math SEO, for example) caused by a conflict of duplicate enqueuing of jQuery Validation UI assets.
• Fixed an issue with switching the view mode of Repeatable Field Groups which stayed disabled because of unsaved changes, even after actually saving changes in the Block Editor.
• Updated the embedded Twig library to prevent PHP 7.4 deprecation notices.

Cosmetics

• Updated strings related to repeatable field options on the Edit Field Group pages.

Fixes

• Prevent unnecessary notice about field group display conditions on the Add New Post page.
• Prevent drafts of Views displaying on the Toolset Dashboard.
• Properly handle storing original file URLs of multiple-value image fields in WordPress 5.3.
• Updated the Installer component to address further WordPress 5.3 compatibility issues.
• Fixed a WordPress 5.3 compatibility issue that was producing a JavaScript error on the Edit Post page.
• Added “themes” to the list of keywords reserved by WordPress and display a warning on the Edit Taxonomy page if a reserved slug is used. This addresses an edge case with WordPress 5.3 and the Featured image functionality in the Block Editor.
• When the Toolset Blocks plugin is active, prioritize it over Layouts on the Toolset Dashboard.
• Improvements in the mechanism for translating a file URL to an attachment ID. This fixes situations when the attachment GUID doesn’t correspond to the actual file subpath for some reason. We’ve also added a Troubleshooting section that allows truncating the toolset_post_guid_id table in case some corruption has occurred and implemented another caching layer to further improve performance when rendering image fields.

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.

Features

• Set the Block Editor as default for newly created custom post types.
• Introduced a new option for the types shortcode attribute show_name='if-not-empty' that will output a field name only when there is a value. This fixes an issue with checkbox fields that are rendered using custom labels for checked and unchecked states (for newly added shortcodes).
• Allow using -1 as an “infinity” limit in toolset_get_related_posts() due to popular demand. However, this is highly discouraged because of performance concerns.

Fixes

• Types will now display a trashed post if it’s already set in a Post Reference Field.
• Added caching to the shortcodes GUI generation.
• Fixed a rare issue with the Address field initialization in the horizontal view of Repeatable Field Groups.
• Fixed an overescaping issue that was breaking non-Latin characters from field options in the “Fields and Views” dialog.
• Fixed an issue with translating Repeatable Field Group fields in the WPML Translation Editor.
• Updated slightly misleading option labels for the Checkbox field.
• Updated messages about conditional display not being available for term and user fields.
• Rephrased an unclear description of the custom update_count_callback taxonomy option.
• Fixed a glitch for file-like repeatable field inputs that started happening in a recent Chrome version.
• Fixed several typos.

Features

• Extend the toolset_connect_posts() function with a possibility to specify an already existing intermediary post for a many-to-many relationship.
• Allow toolset_get_related_posts() function to return Repeatable Field Group items sorted by the manual order set in the user interface.
• Introduced a public API for retrieving custom field groups, field definitions, field types and field instances.
• Added support for the multiple role feature in Toolset Access for user field groups.

Fixes

• Prevented unnecessary TinyMCE initialization when turning a page in the Related Content metabox. Fixed the styling of pagination controls in various listing pages throughout Toolset.
• Internal WPML compatibility fix: Replaced deprecated icl_editor_cf_style and icl_editor_cf_name filters.
• Improvements to determine which field groups should be displayed for a new post with respect to template conditions.
• Fortify the shared class autoloader to prevent a rare PHP warning.

• 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.

• Switching to a scoped version of the Twig library to prevent compatibility issues with third-party software.
• Fixed a are issue where data-dependent field display conditions didn’t work properly in the “Per Post” editor mode when using the classic editor.
• Fixed a wrongly displayed tooltip on the Edit Custom Post Field Group page.
• Updated the Installer component.

• 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.).

• Updated translation files for the plugin’s user interface.
• Fixed an issue where custom field description was being displayed inline with the field label.
• Added a fix to prevent a rare PHP notice when trying to access a non-existent attachment post of an image in a Types custom field.
• Fixed a minor glitch with Repeatable Field Group slug field validation on the Edit Custom Field Group page.
• Fixed a TinyMCE editor issue if there is a WYSIWYG field present in a Repeatable Field Group (the issue did not happen in regular custom field groups).
• Fixed a rare issue with image field thumbnails escaping the thumbnail boundary.

• Introduced the ability to expose custom fields in the REST API.
• Various usability improvements for custom field inputs with main focus on image fields. This includes better drag-and-drop functionality, uploading multiple files at once, and more.
• Fixed an issue where related posts were disconnected when they were trashed from the Related Content metabox (but still, trash all their translations). Also, we now hide trashed posts from the metabox and have improved wording and behavior of affected confirmation dialogs.
• Performance improvements: Various optimizations to reduce the number of database queries that run on every request (or every admin page request).
• Performance improvements: Implement a simple in-memory caching mechanism when working with field groups in order to prevent scaling issues with Relevanssi.
• We now hide the “My templates” post type from Elementor from the “Where to display this Field Group” dialog and from the Toolset Dashboard.
• We now preserve the default user’s settings for displayed metaboxes when saving a post type.
• Fixed an issue with custom field validation not working properly on the Add New post page, when the Block Editor is used.
• Fixed an issue with over-escaping description, title, placeholder and default value of custom fields.
• Fixed an issue where only the first Repeatable Field Group is imported when importing a Module that contains a Custom Field Group featuring multiple Repeatable Field Groups.
• Fixed an issue with missing quicktags in TinyMCE editors for WYSIWYG fields.
• Fixed a bug that occurred when trying to delete a custom field group while legacy post relationships are still being used.
• Fixed a PHP 7.3 compatibility issue.
• We now prevent creating an empty image cache directory when attempting to clear it while it does not exist yet.
• Fixed an issue where some excluded post types have been showing in the Edit Taxonomy page.
• We now display a notice about changing a relationship slug only when the value has actually been changed.
• Fixed a very old bug with data-dependent display condition for field groups that caused other conditions to be ignored.
• We now prevent a caching issue with SiteGround Optimizer that was preventing Repeatable Field Group titles from being saved.
• Fixed issues with inserting files in Repeatable Field Groups and repeatable fields in certain languages.
• Fixed issues with field validation in Repeatable Field Groups where an item was not being expanded on validation error, and newly added items not being validated until the post is saved.
• Fixed an issue where the Post Reference field validation was not triggered in the Block Editor.
• We now make sure that dangling intermediary posts are deleted after a many-to-many relationship is deleted.
• Fixed an issue when an imported module contains a Repeatable Field Group with different group name and slug.
• Provided a workaround for a Gutenberg bug that was causing problems when saving posts with metaboxes in rare cases. See https://github.com/WordPress/gutenberg/issues/15367 for more information.
• Fixed an issue where unsaved input detection before switching a Repeatable Field Group was causing a collision with Avada and Revolution Slider.
• Fixed an issue when displaying read-only values of Repeatable Fields Groups and Post Reference fields in the admin.
• We now make sure that when deleting a custom field group with a Repeatable Field Group and converting it to a post relationship, the child post type with Repeatable Field Group items becomes public.

• Fixed an issue where Custom Field groups appear deactivated on the listing page when using a secondary language.
• Fixed the logic for determining which field groups should be displayed for a particular post.
• Extended the public API functions toolset_get_field_groups() and toolset_get_field_group() and user interfaces for field groups and field definitions. It now allows querying groups by assigned post type.

• Updated the built-in Installer in order to address an upgrade issue that affects some clients.
• Fixed a PHP 7.3 warning about “continue” targeting a switch.
• Fixed an “undefined index” warning on the “Add New Post” page when using WPML Translation Management.
• Fixed a regression from 3.2.5 where Access permission settings have not been properly applied to field groups.

• Make the custom field placeholder and default value translatable via WPML String Translation.
• Updated translation files.
• Fixed a PHP 7.3 warning about “continue” targeting a switch.
• Fixed an issue that expanded RFGs were hidden behind another metabox.
• Fixed an issue with fields from RFGs missing the Fields and Views dialog when editing a Content Template with a page builder.
• Fixed: On the Relationships page, hide screen options which are relevant only for the Edit Relationship screen.
• Fixed: Misplaced WordPress block editor notice about missing JavaScript from the Related Content metabox.
• Fixed: Hide the built-in Blocks post type that is used for storing reusable Gutenberg blocks from the “Where to display this Field Group” dialog.
• Fixed an issue that prevented controlling field groups with non-latin characters in their name by Access.
• Fixed a PHP 5.3 compatibility issue.

• Updated Installer to the latest version.

• Fixed a JavaScript error on the Toolset Settings page when legacy relationships are still being used on the site.
• Fixed an issue where a custom WYSIWYG fields used when creating a new a custom taxonomy term was not being saved.
• Fixed compatibility issues with the horizontal view of Repeatable Field Groups.
• Fixed a regression with the Related Content metabox not showing in the previous version.

• Implemented the “per post” editor mode for post types managed by our plugin. It allows you to select between Gutenberg and classic editors on a per-post basis for a given post type.
• Fixed an issue that occurred when importing post reference fields and repeating field groups, which was introduced with the version 3.2.
• Fixed an error in the Related Content metabox which appeared when WPML was active and a translatable post type was being displayed.

• Fixed issue with frontend form submission when including a Types field with validation.
• Fixed issue with checkboxes field that was displaying separator for unchecked fields.

• Fixed a fatal error on saving post field groups assigned to multiple post types.
• Fixed “padding_color” as attribute for image shortcode not working.

• Prevent browser caching issues on the Related Content metabox.

• Fixed field option “output=raw” rendered shortcodes.
• Fixed image field option “url=true” did not worked for resized images.
• Taxonomies with the attribute “show_ui” set to false will no longer being displayed on the Toolset Dashboard.
• Fixed that “0” as option value was not printed using “output=raw”.
• Yoast Analysis integration for Single-Line, Multi-Line, Image, URL, Post Reference Field and WYSIWYG field types.
• Fixed that RFG items sortorder wasn’t stored for items without field data.
• Respect Toolset Access settings on the relationship table.
• Conditions of Field Groups not respected in Related Posts GUI.
• Support for RFG fields on Module Manager export / import.
• WYSIWYG Fix for Gutenberg.
• Removed the Installer instance priority over other Installer instances.
• Fixed typos.
• Fields under condition in RFG not being saved if the first instance of the RFG does not match the condition.
• Fixed multibyte characters on field group slug were encoded on the metabox id.
• Allow to use other than post-type conditions for field group with RFG / PRF.
• Fixed display issues with the Field Group conditions dialog.
• Prevent a fatal error on the Edit Field Group that is attached to an IPT but does have a generic purpose set.
• Decreased image field rendering time.

• Improved the loading times of Repeatable Filed Groups on the post edit screen.
• Fixing a compatibility issue with Toolset Forms 2.1.

• Fixed types_render_field issue with date and skype fields.
• Fixed orphan RFG relationships when changing RFG slug.
• Fixed submenu items of custom labels for build-in post types were not translatable.
• Fixed issue that made it impossible to change field type on field control page.
• Fixed issue that renaming an RFG field slug caused data loss for all items of the field.
• Fixed attachment deletion when a instance of repetitive images is removed.
• Fixed group display of field when belonging to RFG in field control page.
• Fixed output space character that was being added by non existing value.
• Fixed display glitch while loading custom fields overview page.
• Fixed issue with string translation registration, when saving a relationship.
• Improved date field dialog when WordPress setting includes escaped characters.
• Fixed issues with RFGs that were not excluded from search.
• Fixed issue with Allow resizing of remote images option that stored same-domain resizes on the temporary caching directory.
• Fixed issue with resized images that were not deleted when the original image was deleted.
• Removed fields from field control list, which do not match sanitize_key formatting.
• Fixed image field sizing issue with custom WP_CONTENT_DIR.
• Fixed select field display values not translated with WPML in the frontend when selecting a post in different language.

• Added support for show_name parameter in custom fields.
• Fixed issue with checkbox field that was throwing an error about WPML_CHECKBOX_SELECTED constant.
• Fixed issue with Types shortcodes that were not parsed on the backend.

• Fixed an issue in repeatable field groups that were not working with WooCommerce products.
• Fixed an issue with index attribute of types shortcode for external field types.
• Fixed translation of select field type display values that were not displayed.
• Fixed notice for Toolset registration when only Types and Views lite are active.
• Fixed an issue when importing post group meta using the Module Manager.

• Fixed issue that made it impossible to save fields
• Fixed compatibility issue with Forms Commerce

• Fixed checkboxes saving on relationship table -> quick edit.
• Allowing more than one directive in sprintf in CPT and Taxonomies labels.
• Fixed separated checkbox output showing unchecked options.
• Fixed: CPT of RFG not visible after converting RFG to one-to-many relationship.
• Fixed conditions for nested RFGs.
• Fixed a compatibility issue with jQuery Datepicker and the Related Content metabox (Connect Existing dialog).
• Notify clients migration is not needed for maintaining the legacy relationship.
• Fixed an issue about required Radio Fields fields throw a warning that the field is not saved, even if it is saved, and are not editable.
• Updated Installer to the latest version.

• Fixed an issue when saving checkboxes with same name on legacy relationships.
• Fixed an issue with relationships that were not included in the exported file.
• Fixed an issue with relationships page that was not working properly on Internet Explorer 11.
• Fixed an issue with server port that was displayed in images URL when using SSL.
• Fixed html value of output attribute in Types shortcode.
• Fixed proportional attribute in Types shortcode.
• Fixed raw attribute in types_render_field function that was not working with boolean true.
• Fixed frontend rendering of checkboxes, radio and select fields with special characters.
• Fixed backend rendering of checkboxes fields with special characters on their options.
• Fixed an issue with numeric title of field groups that were not displayed on the post edit screen.
• Fixed a fatal error in Module Manager, when a included relationship was previously deleted.
• Fixed wpt_field_options filter that was not working properly since Types 3.0.
• Fixed a compatibility issue between repeatable field group and Gutenberg.
• Improved the process when moving a repeatable field group that already has some items in posts.
• Improved the process when deleting deleting a repeatable field group, which is now blocked when there are unsaved changes.
• Improved edit link on field group listing page and can be now opened in a new tab.

• Fix: Fatal error in Module Manager when there are relationships with native post types.
• Fix: Include posts in the Pending Review status in results of toolset_get_related_posts() and toolset_get_related_post() by default, and allow for specifying own set of statuses to filter by.
• Fix: An obscure bug where custom field groups weren’t showing in a listing in case a “filter” taxonomy exists on the site.
• Fix: Issues with failed automatic enabling of m2m related to allowed maximum table index size.
• Fix: Saving custom relationship cardinality limits from the Edit Relationship screen.
• Fix: Broken rendering of the types shortcode for term and user fields even if the current post cannot be resolved.

This is the first, very early beta release for the upcoming Types 2.3 version. You can find more information about the biggest new features on the page about creating repeatable field groups and post types relationships with Types.

• Introducing a new way of storing and managing post relationships.
• It is now possible to create many-to-many post relationships.
• Introducing a feature for repeating field groups with infinite nesting.
• Added a new, Post Reference custom field.
• Added a mechanism to migrate from the current post relationship data structures to the new ones.
• Grouped admin menus for the post, user, and term fields into one.
• Lots of other UI improvements.