Hi Paul
I'm not quite sure how it is working in your case, because the extensive testing I have done and my colleague in second tier has done indicate that the user_id is not available with any of the cred_commerce API hooks, and the developers have stated that the user_id of the newly registered user is not available with any of the current hooks, and to make it available would require a feature request.
Let me also repeat what I wrote above, that the email address is a required field in the user registration form.
Now, I know that I've had something along these lines working in the past, despite the statements by the developers, so I persisted in testing myself, starting from scratch, and I've identified how I was able to work with the user_id previously.
Despite not being available directly from the API hooks, the user id gets recorded in a hidden custom field on the WC Order post, with a key of '_cred_post_id'. (With post forms it is the post id, but with user forms this is the user id.)
So, if we use the hook cred_commerce_after_order_completed we have the transaction_id available (which is the id of the WC order), and so we can retrieve the user id from that.
So, in my plain vanilla test site where I have a user registration form with one custom field (company name) and where the username etc. are auto-generated, but which otherwise includes the defaults, then this code works to generate the post based upon the customer name, without error:
/**
* Use the user ID for a newly registered user via WooCommerce
*/
function ts_new_user_id( $data ){
if ( isset( $data['transaction_id'] ) ) {
$order_id = $data['transaction_id'];
$user_id = get_post_meta( $order_id, '_cred_post_id', true );
if ( isset( $user_id ) ){
// Now we have the user ID we can do whatever with it
$company_name = get_user_meta( $user_id, 'wpcf-company-name', true );
$new_post = array(
'post_title' => $company_name,
'post_type' => 'business',
'post_content' => '',
'post_status' => 'publish',
'post_author' => $user_id
);
wp_insert_post( $new_post );
}
}
}
add_action( 'cred_commerce_after_order_completed', 'ts_new_user_id' );
So, where do the errors you describe come in?
Well, all I have to do on my test site to generate the same errors is to remove the email field from the user registration form, then I get the same errors you report.
But the email address is required in a form to register a user. (The GUI lets you delete it, but will be changed so that you cannot.)
Including the email in the user registration form will eliminate the errors.
