The issue here is that the user wanted to ensure that only unique values can be entered into their custom field on their frontend form.
This means that 2 users can't have the same values in the custom fields.
Solution:
You can use the Toolset forms Validation hook to do this.
Add the following hook to your Toolset custom code section in Toolset->Custom Codes and enable it
/**
* CRED custom validation to prevent duplicates CREATE FORM
*/
add_filter( 'cred_form_validate', 'prevent_duplicate_submissions_registration' ,10,2);
function prevent_duplicate_submissions_registration( $error_fields, $form_data) {
$nickname = $_POST['wpcf-form-field']; // Gets value from form
$unique_field = 'wpcf-field-name'; // Meta key stored in db
$form_ids = array( 69696969 ); // Edit IDs of CRED forms
list( $fields,$errors ) = $error_fields;
if ( in_array($form_data['id'], $form_ids ) ) {
// Get existing posts with unique field
$args = array(
'meta_key' => $unique_field,
'meta_value' => $nickname,
'meta_compare' => '=' ,
);
$matching = new WP_User_Query( $args );
$results = $matching->get_results();
if ( !empty( $results ) ) {
$errors[ $unique_field ] = $nickname . ' is already in use. Choose a different name.';
}
}
return array($fields,$errors);
};
/**
* CRED custom validation to prevent duplicates EDIT FORM - excludes current user from the query as it will find a matching nickname
*/
add_filter( 'cred_form_validate', 'prevent_duplicate_submissions' ,10,2);
function prevent_duplicate_submissions( $error_fields, $form_data) {
$current_user = get_current_user_id();
$nickname = $_POST['wpcf-form-field']; // Gets value from form
$unique_field = 'wpcf-field-name'; // Meta key stored in db
$form_ids = array( 420420 ); // Edit IDs of CRED forms
list( $fields,$errors ) = $error_fields;
if ( in_array($form_data['id'], $form_ids ) ) {
// Get existing posts with unique field
$args = array(
'meta_key' => $unique_field,
'meta_value' => $nickname,
'meta_compare' => '=' ,
'exclude' => $current_user
);
$matching = new WP_User_Query( $args );
$results = $matching->get_results();
if ( !empty( $results ) ) {
$errors[ $unique_field ] = $nickname . ' is already in use. Choose a different name.';
}
}
return array($fields,$errors);
};
Note this is for a user form and will need to be customized to work for posts, however in the case of a user form you will need to change the wpcf-form-field and wpcf-field-name to the slug of the field that you want to prevent the duplicate on while keeping the wpcf- prefix on the field slug.
Problem: I would like for Guests to be able to create content on my site. Once the content is approved, then I would like for the guest to register as a User. At that point, I would like for the new User to be listed as the author of the post created earlier by the guest User.
Solution: You could ask guests to fill in their email address when they submit content, but there's no guarantee that this will match up with the email address they use when they sign up or register. Then when they do register later, even if they use the same email address, there's not an automated way to retroactively assign them as author to the content they created. It sounds like automating this full process would require a significant amount of custom code. You'll need some way to associate guest authors with future users, and to automate the retroactive author assignment somehow.
Otherwise the workflow will be fairly manual, because some Editor or Admin user will be required to manually go in and change the author of the posts created by Guests after the Guest signs up and becomes a User. If the email address provided earlier matches with the User's email address, it will be easy to do this from wp-admin. If it does not match, it will take some additional work to contact new Users and determine which should be the author.
Problem: I have created a custom post type, but when I try to create a CRED form that will allow me to create posts, I cannot select my post type because it's not visible in the list of options.
Solution: Check the post type options - it should be publicly queryable.
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.
