Support

February 13, 2019 at 10:18 am

Hi there,

I tested this on a couple of my test sites and the initial registration shows up on the accounts for those sites. Checking through the code of the WP User integration add-on it specifically checks if it has created a new user and links the users to the EE contact for the registration.

Something I did notice on your site, is the link to register for an account (THIS) is using a checkout session. I looks like you’ve customized the new user registration process to try and use EE’s registration form, however, whatever you are doing to force EE past the user check it likely what is breaking your ‘first’ registration as it will be linked to whatever the ‘current’ user is during that first registration?

February 15, 2019 at 2:30 am

Can you please suggest a specific solution to achieve this?

At what point in the registration do you want to make the call?

For example, what if someone registers onto the event but does not actually pay? Do you still want to make the call?

You’ll need to be specific on when you want to make the additional call as it will affect the hook you can use to do so.

In either case, this seems to be a different issue than the above?

February 21, 2019 at 7:22 am

Before going into 3rd party requests on specific actions, wouldn’t it be best to fix the above issue first? Right now your first registration isn’t linked to your WP user account because of how the site is set up.

Adding additional requests based on that current behaviour and then changing that behaviour will likely mean the below is no longer valid.

If the user registered and did not purchase any event at that time also I want to hit API and insert data to the third party

The problem with that is you are using EE as the main WP User registration on your site, for example, the link to register a new user on your site links to an EE checkout form, that’s not expected and not how the WP User integration was intended to be used.

When the WP user integration add-on creates a user it fires this action:

AHEE__EED_WP_Users_SPCO__process_wpuser_for_attendee__user_user_created

When it updates a user it first this action:

AHEE__EED_WP_Users_SPCO__process_wpuser_for_attendee__user_user_updated

You can hook into those to make a request, but again, I have no idea if that will work as expected due to your setup, it’s not standard.

In case of purchasing event I will use a PUT request to update event against the same user.

You can use the same hook the WP User integration add-on uses to do its processing (you need the same data right?)

AHEE__EE_Single_Page_Checkout__process_attendee_information__end

Take a look in \eea-user-intergration\EED_WP_Users_SPCO.module.php for example of how you can pull the information you need.

So I am need of two hooks first is at successful registration and one at successful payment.

With regards to the latter, after payment, do you want the hook to first with ANY payment made on a registration or only when the registration is updated to be ‘Approved’? (Meaning the registration was paid in full or the admin manually set the status to Approved)

Apart from these one more I found is that at time of the successful registration user is not receiving an e-mail with account info only receiving payment/event detail emails.

Its still not clear if the WP User integration is actually adding the WP User or something else, the emails in question are generated by WordPress itself, EE creates a user using wp_create_user() which automatically triggers a new user notification email from WordPress.

Have you confirm they are not going to spam?