Problem: I have a CRED Create User form that includes the first_name field. I would like to prevent Users from submitting an email address in this field.
Solution: The only way to implement this type of validation is to use PHP code on the backend and the cred_form_validate API. Then you could set up a custom regex or other string validation system to test the first name entered and return an error if necessary. Here's a simple example using the validation API to test the first name value:
add_filter('cred_form_validate','no_email_name_validation',10,2);
function no_email_name_validation($error_fields, $form_data)
{
//field data are field values and errors
list($fields,$errors)=$error_fields;
//uncomment this if you want to print the field values
//print_r($fields);
//validate if specific form
if ($form_data['id']==12345)
{
//check first name value
if ($fields['wpcf-first_name']['value']!='John')
{
//set error message for my_field
$errors['wpcf-first_name']='Only members named John are allowed'';
}
}
//return result
return array($fields,$errors);
}
Replace 12345 with the numeric ID of your CRED user form, and modify the conditional using your own custom validation code.
Problem: It seems like the Package Order number is incorrect on the Classifieds site "Manage My Listing Packages" page. It shows the WooCommerce Order number minus 1. It seems like these should be the same number.
Solution: The reason these numbers are different is that WooCommerce "Orders" and post type "Packages" are not the same thing. In the admin area, these two concepts are represented by two different Post Types - the WooCommerce Order and the Package post type. They are related, but not identical. Orders are used by WooCommerce to track purchases, Packages are used in the system to manage advertisements. The reason the numbers are sequential is because these two things are created sequentially when you submit the CRED Commerce form and then checkout, and WordPress uses sequential numeric IDs. A hidden field connects these two posts in the database so the Package can be updated automatically when the Order status changes.
You can see the two different items by going to WooCommerce > Orders, or by going to Packages > All items.
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.
