Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Suggested location to add a "post completed transction" action? | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Suggested location to add a "post completed transction" action?

Suggested location to add a "post completed transction" action?

Posted: July 1, 2013 at 1:07 am

Viewing 1 reply thread


Richard Teachout

July 1, 2013 at 1:07 am

Just looking for your “best practice” suggestion…

What would be the best place to put (or use existing) hook, so that when event espresso has fully completed a sale, I can make a web request to another site (the software where our on-premise ticket sales and accounting takes place) and use that API to add the transaction? I already have the PHP to consume that API, I just need to know where/how the best place to implement the outside link. I anticipate it to be somewhere in the process_payments section, maybe at the end of espresso_email_after_payment (so it only records it once a payment has been made not when a transaction was created without payment)? I definitely want it to have access to the data of the transaction data itself, so I can repost some important data to the accounting system.

So hence, what would the best place be, so future upgrades don’t totally botch this addon code? (or does it with the least impact)

Thanks!


Josh

July 1, 2013 at 11:04 am

Hi Richard,

It sounds like you can use the action_hook_espresso_track_succesful_sale hook for this.

Viewing 1 reply thread

The support post ‘Suggested location to add a "post completed transction" action?’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso - Staging Server