Problem: I am trying to validate a custom field with cred_form_validate, but I cannot validate a specific field. Errors never appear in the form.
Solution: Be sure to include the form_messages field in the Form builder so errors can be displayed. Then use the following syntax to validate a custom field:
function fn_cred_form_validate($error_fields, $form_data)
{
list($fields,$errors)=$error_fields;
if ($form_data['id']==221) {
if (empty($fields['wpcf-application-tour-number']['value'])) {
//set error message for my_field
$errors['application-tour-number']='Please select tour first';
}
}
return array($fields,$errors);
}
add_filter('cred_form_validate','fn_cred_form_validate',10,2);
Notice that the wpcf- prefix is required in the $fields array, but should not be included in the $errors array.
Problem: I have defined a custom field in my Form and set its value using a URL parameter. I would like to hide that field on the front-end, but if I use HTML comments the field value is not saved. How can I hide the field but save the value from a URL parameter?
Solution: Use CSS to hide the field itself or a container element:
Problem: I am using a Fields and Text block to display some text, including the post slug. I have set the text-transform property for this block to be "uppercase" but the slug always displays in lowercase.
Solution: It seems that GeneratePress includes some styles for H1 elements that includes the property text-transform: none;, and you would have to override that using custom CSS. Add the CSS class tb-uppercase-override to the Fields and Text block, then add this CSS in the template, an enqueued CSS file, or in Appearance > Customize > Additional CSS:
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.
