Trisy123

Ah that’s great! I’ll be waiting! ??

Btw. Amazing plugin! I use it every day!

Hi John, I just discovered an update for the Woochimp plugin and that seems to have solved it. Perhaps the cookie was used. We’ll never know.

Thanks for your input and time!

We are on 2.6.4 so that means it’s not woocommerce related. Probably.

This issue became known this week for me. But that doesn’t tell much more. Our Chrome could have update later than yours. Another possibility I was thinking of is Woocommerce updates. Another option could be the acrobat/pdf creator on the machine being updated.

I will do some more in-depth tests soon.

Just to make sure this subject is being looked at. I have the exact same issue.

In Chrome, if you print one, it’s fine.
In Chrome, printing more than one, the header as described by @northwestdesign appears.

It doesn’t make much sense to me but something is going wrong.

This is probably what is causing issues for me too. It would be nice if the dev would look into this.

Solved!

Okay it works! Sadly I had to put it straight into my login hook or it wouldn’t work. Now I just need to figure out how to get my notify mail rolling again.

Great documentation btw! Very useful!

add_action( 'wpmem_post_register_data', 'my_registration_hook', 1 );
function my_registration_hook( $fields ) {
	$creds = array();
	$creds['user_login']    = $fields['username'];
	$creds['user_password'] = $fields['password'];
	$creds['remember']      = false;

    $first_name = $fields['billing_first_name'];
    $last_name = $fields['billing_last_name'];

    update_user_meta($fields['ID'], 'first_name', $first_name);
    update_user_meta($fields['ID'], 'last_name', $last_name);

	$user = wp_signon( $creds, is_ssl() );
	if ( ! is_wp_error( $user ) ) {
	wp_redirect( $_SERVER['REQUEST_URI'] );
		exit();
	} else {
		return "loginfailed";
	}
}

So I wrote this:

add_action( 'wpmem_post_register_data', 'wp_mem_savename', 1 );
function wp_mem_savename( $fields ) {

    $first_name = $fields['billing_first_name'];
    $last_name = $fields['billing_last_name'];
    $user_ID = get_current_user_id();

    if( (!empty($first_name)) && (!empty($last_name)) ){
        update_user_meta($user_ID, 'first_name', $first_name);
        update_user_meta($user_ID, 'last_name', $last_name);
    } else {
        return;
    }
}

But then I realised that the user isn’t logged in at this stage. How would I write in a user if it’s not logged in and the ID has yet to be created?

Thank you for the info, but could someone tell me how to make it login AND send the notification email? ??

Again I’m being completely ignored by IgniteWoo.
Such a nice way to treat your paying customers.

Your function is exiting the registration function

So, instead of hooking it into wpmem_register_redirect, Wouldn’t it make more sense to remove/replace our Exit(); With something that continues to run the needed scripts?

However, I did try replacing the hook but it seems it’s no longer able to grab the fields and log in. So I am afraid I cannot really work with that.

Edit:
Removing the exit(); will indeed cause it to continue what it should do. But it also somehow makes it not login.

I can however confirm that this is indeed causing the mails to be sent or not.

I forgot to inform you that this was in my functions.php

The following code was added.

add_action( 'wpmem_post_register_data', 'my_registration_hook', 1 );
function my_registration_hook( $fields ) {
	$creds = array();
	$creds['user_login']    = $fields['username'];
	$creds['user_password'] = $fields['password'];
	$creds['remember']      = false;
	$user = wp_signon( $creds, is_ssl() );
	if ( ! is_wp_error( $user ) ) {
	wp_redirect( $_SERVER['REQUEST_URI'] );
		exit();
	} else {
		return "loginfailed";
	}
}

Could this mess with the email being sent?

The account was indeed on my side, excuse me for that.

Please check your records on ‘Tristan’ Forgot all previous requested support. I’ve managed to solve that in some other ways. I have however requested new support about the phone order plugin, the documentation for this plugin is just as bare as the plugin options itself. All I need is an extra field to save to a user data field.