Problem: I would like to use different submit buttons in a Form to allow Users to change the post status manually. One button for "Pending Review", one button for "Publish", etc.
Solution: You can create 4 Forms, one for each post status. Remove the other input fields except the main CRED form shortcodes and the submit button shortcode. If the Form's only purpose is to modify the status of the post, then this could work.
Problem:
The output of an existing View now includes wrapper divs with classes of .et-boc and .et_builder_inner_content which messes with the current style rules.
Solution:
Divi introduced this change—which even affects Views where the template is *not* designed with Divi—in version 3.10.1.
After many user complaints about side-effects it is expected to be removed in subsequent Divi versions.
Problem: I would like to enforce file type restrictions on a file upload field in a Form, but the cred_form_validate hook does not provide any information about the file uploads.
Solution: Use the cred_file_upload_disable_progress_bar hook to inspect AJAX file uploads. Inspect the $_FILES superglobal to retrieve file metadata.
//*Validate for PDF on File Upload
add_filter('cred_form_ajax_upload_validate','cred_filetype_validation',10,2);
function cred_filetype_validation($error_fields, $form_data)
{
$file_types = array('application/pdf','image/jpeg','image/png','image/tiff','image/gif');
// Field data are field values and errors
list($fields,$errors)=$error_fields;
//Run the rest of code for this CRED ONLY and IF the file is upload type and size are set.
if (in_array($form_data['id'], [654,836,848]) && (isset($_FILES['wpcf-pedigree']['type']))) {
//Retrieve file type
$file_type_uploaded=$_FILES['wpcf-pedigree']['type'];
//Validate files uploaded, make sure its PDF file type
if (!in_array($file_type_uploaded, $file_types) ) {
//Validation failed,
// set error message per field
//Remove wpcf - prefix here!
$errors['pedigree']='Sorry the file you have uploaded is not of the correct type. Accepted file types: pdf, jpg, gif, png, tiff';
}
}
//return result
return array($fields,$errors);
}
Problem: I am trying to use a distance filter in a WordPress Archive but it does not seem to be working.
Solution: Distance filters in WordPress Archives are not currently functional. We hope to fully support this feature in an upcoming release, but for now, the best approach is to create a View with a distance filter and insert it in a WordPress Archive. Remove everything in the wpv-loop tags of the Wordpress Archive's Loop Output editor.
In a CRED form for creating post, We initially had a post taxonomy term select field that was automatically populated based on the page it was on. These industry pages were given the same custom taxonomy we created for the CPT post that was to be created from these forms, and assigned the appropriate taxonomy term to match the term the post needed to go to. The idea was that the user shouldn't have to worry about selecting an option from a "Choose Industry" field when they're already on a page designating the industry they're interested in.
We had it working, but for whatever reason it no longer is, so I'm wondering if there was a PHP solution that I could utilize for this case.
Solution:
There isn't such a built-in feature within CRED forms, see our document:
When user submit the CRED form, you can use CRED action hook "cred_save_data" to trigger a PHP function, and save the "industry" value into database, see documents:
Problem: I am trying to display a map on my child post, and insert a marker using the address field of a parent post. The marker is not appearing and the map is showing the ocean.
Solution: Ensure the address field is set correctly, and use the id operator and specify the parent post type slug in the marker shortcode:
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.
