Problem:
When creating a notification in a Toolset Form, it should be possible to choose an email field from the form itself as the recipient, but it is not working.
Solution:
There was a bug that prevented an email field from being selected if it used the value attribute to set a default email address. This was fixed in Forms 2.1
Problem:
Since the release of Types 3.0, repeatable field groups and post reference fields are not working with WooCommerce products or other 3rd party custom post types.
Problem: I have a numeric field in Types, but when I include the field in a Form it is input type="text". I would like to use input type="number".
Solution: At this time, Types and Forms only support input type="text". We have a feature request in place to improve this functionality, but I don't have an implementation schedule just yet.
Problem:
When you insert a CRED Edit Form to a Page and use the post='' attribute of the CRED Edit Form shortcode to specify which post to edit, and the form features any type of checkboxes (including taxonomy checkboxes), these checkboxes will always be displayed as unchecked on the front-end form. This happens no matter what you saved in the backend when editing the post.
Solution:
Yes, you are right, the custom field settings is stored in the table wp_options, field slug is "wpcf-fields", you can get it the field description using the PHP codes you mentioned above:
We document known issues and their solutions in Toolset errata. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.
Support Policy
Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.
Please make sure to issue only one topic per each support ticket.
