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
An instant payment notification failed gateway variable dump | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › An instant payment notification failed gateway variable dump

An instant payment notification failed gateway variable dump

Posted: January 29, 2013 at 4:01 pm

Viewing 4 reply threads


Jon

January 29, 2013 at 4:01 pm

Receiving an error when a payment fails, the only problem is it keeps repeating and sending the error via email up to 2000 times. I am using NAB Direct Post as a gateway.


Josh

January 30, 2013 at 4:06 pm

Hi Jon,

Which version of Event Espresso, and are there any other gateways active?


Jon

January 30, 2013 at 5:46 pm

Hi Josh,

I am using version 3.1.29.1P

And the gateways active are NAB transact direct post and Check/Money Order.


Josh

January 31, 2013 at 9:45 am

Hi Jon,

I’m not sure why it would be sending out 2000 IPN variable dump emails. It’s only supposed to fire that email once, unless NAB continues to resend more IPN failures to your site.

You could try commenting out line 37 on nabpaymentprocess.php and that will disable the email notifications for IPN failures.


Jon

January 31, 2013 at 8:13 pm

Seems to have done the trick. Thanks Josh!
Viewing 4 reply threads

The support post ‘An instant payment notification failed gateway variable dump’ 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.

The original Forum description...

Status: closed

Updated by Jon 11 years, 11 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: resolved
Event Espresso - Staging Server