Problem: I would like to be able to see form validation messages after I submit a CRED form, but when the page reloads my CRED form is not visible. Therefore my Users have no way of knowing that their submission was not successful.
Solution: At this time, the best option is to use AJAX updates for this form.
Problem: I would like to add custom validation to a CRED form using the cred_form_validate hook. Some fields are required based on the selections in other fields, and I can't accomplish this in wp-admin.
Solution:
Modify the cred_form_validate to work for your site's requirements:
add_filter('cred_form_validate','form_field_validation', 2, 10);
function form_field_validation( $field_data, $form_data ) {
// field data are field values and errors
list($fields,$errors)=$field_data;
// validate if "sell" CRED form ID
if ( $form_data['id'] == 1234 ) {
// add validation code for each field like shown here
if ( $fields['wpcf-text-field']['value'] == '' )
$errors['text-field'] = 'Text Field must not be empty';
if ( $fields['wpcf-other-field']['value'] == '' )
$errors['other-field'] = 'Text Field must not be empty';
}
// validate if "missing" CRED form ID
if ( $form_data['id'] == 6789 ) {
// validation example for a multi-step requirement
if ( ( $fields['wpcf-checkbox']['value'] == '' ) && ( $fields['wpcf-checkbox-2']['value'] == '' ) )
$errors['checkbox-2'] = 'Checkbox 2 is required if Checkbox 1 is checked';
}
return array( $fields, $errors );
}
Problem: I have a CRED form that includes an optional image field. If the User submits the form without including an image in the field, I would like to automatically choose 1 of 4 placeholder default images at random.
Solution:
Add this custom code to your child theme's functions.php file:
add_action('cred_save_data', 'cred_add_default_img_action',10,2);
function cred_add_default_img_action($post_id, $form_data)
{
$forms = array( 1234, 5678 );
// if a specific form
if (in_array($form_data['id'], $forms))
{
if (!isset($_POST['wpcf-slug']))
{
$pics = array(
"http://yoursite.com/path/to/image1.jpg",
"http://yoursite.com/path/to/image2.jpg",
"http://yoursite.com/path/to/image3.jpg",
"http://yoursite.com/path/to/image4.jpg",
);
add_post_meta( $post_id, 'wpcf-slug', $pics[ rand( 0,3 ) ] );
}
}
}
Replace 1234, 5678 with a comma-separated list of CRED form IDs where you want to apply this code. Replace 'wpcf-slug' with your field slug, and add the 'wpcf-' prefix, replace the 4 URLs with the actual image URLs on your site. If you choose not to use 4 options, replace the '3' in 0,3 with a number one less than the number of default options.
I noticed that whenever a CRED Form is submitted to create a post, an exact or maybe different copy of the same post (duplicate) is created that has the title like "AutoDraft..."
Why?
Solution
There are 2 Bugs provoking this issue.
One with Relevannsi, and one with SEO by Yoast and Elementor.
The last one has no patch yet, the first has one.
Problem:
How can I alter Custom Fields in a CRED Form, which are already required in Types, so that they become voluntary?
Or- how can I do the opposite. Requiring a field on CRED, but not making it required in Types?
Solution:
You have the choice to use CRED Conditionals here.
1. To make a Field not required, which is required in Types:
- create a required Field in Types
- add it to your CRED Form
- wrap it in a CRED Conditional, so to show it only if a particular other condition is met.
As long that another condition is not met (as in "value of another field in the CRED Form"), this required field is not shown on the Form, and hence, not required anymore.
2. To make a field required, which is not required in Types:
- create a non-required field in Types
- add it to your CRED Form
- wrap the CRED Submit ShortCode in a CRED Conditional that shows the Submit Button only if the field you want to require is filled (value is not empty).
Problem:
When I style a Content Template with Beaver Builder and then display this in a page, which is also styled by Beaver Builder, then the CSS applied with the builder is not shown on the front end.
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.
