Support

February 3, 2020 at 4:30 am

I used the new hook you suggested FHEE__EE_SPCO_Reg_Step_Attendee_Information___process_registrations__pre_registration_process but I can no longer access/echo the registration questions via $data anymore.

Yeah, you won’t be able to just echo out the contents on the current page because the above runs on an ajax request.

You’ll need to log the details rather than output them, then view the log. Or capture the ajax request and see what is output on that.

Open Chrome dev tools, go to the Network tab and then click the submit button on checkout, you’ll see an admin-ajax.php request, view that.

As a check. I tried to simply EED_WP_Users_SPCO::verify_user_access(); during the filter hook you recommended and it returns ‘This transaction cannot be processed. Please refresh and try again.’. How come this happens?

What exactly did you try? EED_WP_Users_SPCO::verify_user_access(); isn’t going to work as your not passing any of the request variables to the method but there may be some other error, check your error logs to confirm.

Have I gone completely off the rails Tony?

Possibly, although I can’t tell from the code you provided as it makes no sense out of context 🙂

Does this thread provide clues to the solution I seek?

Not as far as I can tell.

—

Again I recommend you go back to the verify_user_access method and step through how it works, not how to call it, but what it is doing and how it stops the registration process. That method already shows you how to do most of what you are tyring to do, is using different fields but it’s all there.

You may need to contact a developer familiar with OOP to help with this.

February 3, 2020 at 2:48 pm

Can you comment on how it is determined what variables are available when one hooks into a filter/action with a function?

You need to take a deeper look at WordPress hooks and how they work, my recommendation for this is to go over this:

https://www.smashingmagazine.com/2011/10/definitive-guide-wordpress-hooks/

The short answer is you look in the code to view where the hook is applied and view the variables passed to the hook.

So in the case of FHEE__EE_SPCO_Reg_Step_Attendee_Information___process_registrations__pre_registration_process you’d search the EE4 core codebase for the above and eventually find:

event-espresso-core-reg\modules\single_page_checkout\reg_steps\attendee_information\EE_SPCO_Reg_Step_Attendee_Information.class.php::_process_registrations()

Within that method the above hook is applied, like this:

apply_filters(
    'FHEE__EE_SPCO_Reg_Step_Attendee_Information___process_registrations__pre_registration_process',
    false,
    $att_nmbr,
    $registration,
    $registrations,
    $valid_data,
    $this
)

The first value is the value being filtered (in this case a flag for whether or not to stop processing), the others are additional variables you can use. So this:

My original theory was, whatever arguments are passed onto apply_filters(‘plugin_hook’,false, $arg1, $arg2) are available for use in custom functions.

Is correct.

Upon, checking admin-ajax.php after doing print_r on the variables from apply_filters, they seem very different that $registration

This doesn’t really mean anything to me as the function your hooking in with could call any variable whatever if wants….

I’ve seen elsewhere. In other threads, people were able to access methods in $registration like $registration->ID(), but when I do it using the suggested hook, it returns a fatal error.

If they have a valid EE_Registration object, then sure, that would work, but again your custom function could be doing anything, so that really doesn’t mean much. You’ll need to give clearer examples of the code your running and what it returns as without context I really can’t give you any information.

Why are/Are there like 5 different $registrations?

This is another example of a question I can’t answer without context, I have no idea where you are getting 5 registrations from, nor where EE is apparently pulling them from, without the context of the code.

Through sheer random brute force, I happened to try printing $item to admin-ajax.php. To my amazement, it contained the submitted registration form data, including the fields I need to custom validate.

??? What is $item?

Add the code you used for this to a gist or pastebin and I’ll take a look, however note that generally we (EE Support) will not provide support for customizations. I’ll take a look over and see if I can help point you in the right direction but note that the answer may well be to contact a developer familiar with WP and OOP for further help.

How could I have discovered that $item was available before?

Take a look over the link I provided for how to use hooks, it explains this in detail.

For learning purposes, what other variable/method could I have used to access the data contained in $item?

This needs more context, I have no idea what $item is here.

February 3, 2020 at 4:52 pm

the array $item wasn’t in apply_filters for the hook, but it contains all the form data submitted and I personally did not create the variable $item.

Yes, you did.

You created it in in your own callback function that is hooking in.

The variable names you use mean very little (although the should make logical sense with the data passed to them), but the order of your arguments matter, a lot.

Where does $item come from?

Here:

function extra_validation( $registration, $registrations, $valid_data, $att_nmbr, $item)

You’re callback is using the parameters passed on the hook, but it is using them incorrectly. The variable names are your own, you can call them whatever you want but the order matters, as that is how the hook passes the data over to your function. So with your above function, you are hooking into the filter and its passing data over to your function:

apply_filters(
    'FHEE__EE_SPCO_Reg_Step_Attendee_Information___process_registrations__pre_registration_process',
    false, // You set this into $registration
    $att_nmbr, // This into $registration
    $registration, // This is $valid_data.
    $registrations, // $att_nmber
    $valid_data, // $item
    $this // not used
)

So in your function, $valid_data from the hook is passed into $item.

You create $item, with a local scope to your function.

The above is why I couldn’t answer your questions previously as it makes no sense outside of your own callback function. $item could have been anything at all in the arguments passed above.

The short answer is to change your callback function to pass the data correctly so you can use it:

function extra_validation( $stop_registration, $att_number, $registration, $registrations, $valid_data, $att_reg_step) {
    print_r($valid_data);
    $stop_registration = true;
    return $stop_registration;
}

That will output exactly the same as what you had before, but now you have all of the data passed to your callback in variables that match/make sense with what the hook is passing.

How can I determine all the variables (such as $item or $data) available for use for a particular hook?

I explained that in my previous post, if you need additional details you’ll need to work through the link I provided to understand hooks.

Working with WordPress (and Event Espresso) revolves around hooks, if you don’t understand the fundamentals of how they work you’ll struggle with each and every piece of code you write for either.

here’s the output from admin-ajax.php, it contains the registration data:

Yeah, your setting whatever is in $valid_data to $item then outputting that to the browser.