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
Bug with PayTrace payment gateway (still unresolved) | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Bug with PayTrace payment gateway (still unresolved)

Bug with PayTrace payment gateway (still unresolved)

Posted: March 5, 2013 at 10:11 am

Viewing 2 reply threads


Bri Laub

March 5, 2013 at 10:11 am

The latest version of Event Espresso says that this bug has been fixed (here is the thread discussing it), but it is not fixed. I’m still having the same issue as before.


Bri Laub

March 5, 2013 at 10:19 am

Ah, it looks like maybe this was addressed in this latest release. There is a “quickpay / paytrace bugfix” fix in September of 2012, but that must have been something else.


Josh

March 5, 2013 at 10:23 am

Hi Bri,

The PayTrace payment gateway was fixed in Event Espresso 3.1.31. The .30 versions did not include the fix. You can download the 3.1.31.beta from your account page by checking the box that opts you into the pre-release channel.
Viewing 2 reply threads

The support post ‘Bug with PayTrace payment gateway (still unresolved)’ 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 Josh 11 years, 10 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server