Support

November 30, 2020 at 4:55 am

Hi there,

Without trying to bash your code here, there is a fair amount wrong with that code.

function eccent_ee_transaction_success($event_queue) {

Why $event_queue?

The AHEE__thank_you_page_overview_template__content hook is passed the EE_Transaction object which is all you need to pull all of the information you need, but using it as an event_queue is misleading as that’s not what it is. Switch that to $transaction and use is as the EE_transaction for the current registrations.

Meaning $reg = $event_queue->registrations();

Now becomes $regs = $transaction->registrations();

It makes more sense now that you’re pulling the registrations from the transaction into $regs, right? So its an array for EE_Registrations linked to the current EE_Transaction, even if that’s just a single registration.

foreach ($reg as $key) {
    // loop through and use the get method to extract the protected data
    // echo $key->get('TXN_ID'); 
    // echo '<br>';
    array_push($txn_ids, $key->get('TXN_ID'));
}

echo '<strong>Transaction IDS From This Transaction:</strong><br>';
echo var_dump($txn_ids);
echo '<br><br>';

$transactions = EEM_Transaction::instance()->get_all(
    array(
        'limit' => 10,
        array(
            'STS_ID' => 'TCM',
                'TXN_ID' => $txn_ids[0]
        ) 
    ) 
);

None of this is needed, your using the EE_Transaction to pull all of the registrations linked to that transaction, to then pull an EE_Transaction using the TXN_ID from each of the regs (which will be exactly the same for them all) to then use get_all on the EEM_Transaction model to pull the exact same EE_Transaction that is currently passed to the filter.

So, $transaction already holds this object for you and you can skip all of this.

This:

echo '<strong>Attendee Data Using First Index of Transaction IDS:</strong><br>';
foreach( $transactions as $transaction ) {
    // echo 'txn_id: '.$transaction->ID().'&nbsp;';
    $reg_att = $transaction->get_first_related( 'Registration' );
    if ( $reg_att instanceof EE_Registration ) {
            $att = $reg_att->attendee();
            if ( $att instanceof EE_Attendee ) {
                $att_id = $reg_att->attendee()->get( 'ATT_ID' );
                echo var_dump($att);

                //for($x = 0; $x < count($att); $x++) {
                //    $att_temp = $att[$x];
                //    echo $att_temp;
                //}

                //$args = array(
                //    'meta_key'   => $wpdb->prefix . 'EE_Attendee_ID',
                //    'meta_value' => $att_id,
                //);
                //$wp_user_query  = new WP_User_Query( $args );
                //if ( ! empty( $wp_user_query->results ) ){
                //    $users = $wp_user_query->get_results();
                //    foreach ( $users as $user ) {
                //        echo 'User ID: ' . $user->ID . '<br>';
                //    }
                //} else {
                //    echo 'No user found<br>';
                //}
            }
        }                               
    }
}

Is backwards within Event Espresso, the EE_Transaction groups the registrations so you use the EE_Transaction to pull EE_Registrations, then loop over the registrations to pull the data relevant to the specific registrations (including the attendee as that is related to the registration).

Your looping over ‘transactions’ (which will actually just be one) and then using the transaction, to pull the first related registration (which make sense, but not within this loop) to pull the attendee etc.

Again, my intention is not to pick away at your code here but if I don’t give you the above details you’ll be going around in circles for nothing. You need to take a look at the documentation for the model system here:

https://github.com/eventespresso/event-espresso-core/tree/master/docs/G–Model-System

The reason I say that is the models make this really simple to do, but you obviously need to understand the models to do it. In this case, most of your code above can be replaced with:

$regs = $transaction->registrations();
foreach( $regs as $reg ) {
    if( $reg instanceof EE_Registration ) {
        $attendee = $reg->attendee();
        if( $attendee instanceof EE_Attendee ) {
            echo $attendee->email();
        }
    }
}

With regards to your WP_User_Query, there’s a method already available to do that query within the WP User integration add-on (which I assume you have active otherwise it wouldnt’ be worth pulling that data :))

See EE_WPUsers::get_attendee_user($attendee->ID());

So your whole snippet becomes something like:

function eccent_ee_transaction_success($transaction) {
    //Pull all the registrations related to the transaction.
    $regs = $transaction->registrations();
    // Loop over each registration.
    foreach( $regs as $reg ) {
        // Confirm we have an EE_Registration object.
        if( $reg instanceof EE_Registration ) {
            // Pull the EE_Contact liked to the registration.
            $attendee = $reg->attendee();
            if( $attendee instanceof EE_Attendee ) {
                // Use the EE_Contact to output the email address.
                echo $attendee->email();
                // Or whatever else you want to do with the attendee details here.
               
                // Do we have a User account linked with this EE_Contact?
                $user_id = EE_WPUsers::get_attendee_user($attendee->ID());
                if(! empty($user_id) ) {
                    //$user_id holds the ID of the WP_User account liked to this EE_Contact, do something here.
                }
            }
        }
    }
}
add_action('AHEE__thank_you_page_overview_template__content', 'eccent_ee_transaction_success', 10, 1);

Using the models to pull the data in the way it is intended to be makes the code much easier to follow here.

What I usually recommend you do when trying to find the methods on the objects you have available is use kint:

https://wordpress.org/plugins/kint-debugger/

Wrap the object in d(); and you’ll get a really nice output showing all of the methods available and various other info. So:

$attendee = $reg->attendee();
d($attendee);

Would have given you a full list of the methods available on the object, such as email().

Side note – all of the code above is untested, I’ve written it here on the forums based on your snippet, there may well be a typo or syntax error above that I’m missing.