A Toolset Form was used to save an iframe embed code into a custom field (event-map) using [cred_field ...], but the iframe was being stripped from the submitted content and not saved. The user had already tried allowing iframe via the wp_kses_allowed_html filter, but it still didn’t persist. The behavior had worked previously and later stopped.
Solution:
Enable iframe support in Toolset’s own Forms Content Filter so Toolset Forms stops stripping the tag:
Go to Toolset → Settings → Forms → Content Filter
Click “Select allowed HTML tags”
Enable iframe and save
Also ensure the embed code is stored in a Multiple Lines (or WYSIWYG) field rather than a Single Line field to prevent truncation/format issues.
A custom Toolset user field (wpcf-number-of-bookings) was initialized with a value of 0 when a user was created. However, when editing and saving the user from WordPress Dashboard → Edit User, the value 0 was cleared and saved as empty, even when the field type was set as a single-line text or number field. This behavior occurred consistently across multiple sites.
Solution:
A PHP hook was added to listen to the profile_update action. After the user profile is saved, the code checks whether the custom user meta field is empty or null. If so, it explicitly resets the value back to "0" using update_user_meta(). This ensures that zero values persist after saving the user profile in the WordPress admin.
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.
