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
QuickPay not recording transaction/reg/payment ID | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › QuickPay not recording transaction/reg/payment ID

QuickPay not recording transaction/reg/payment ID

Posted: November 22, 2012 at 9:56 am

Viewing 2 reply threads


Runemester

November 22, 2012 at 9:56 am

22-5075367dbe725


Sidney Harrell

  • Support Staff

    •

November 23, 2012 at 7:33 am

You can change line 8 of gateways/quickpay/quickpay_vars.php to be:

$ordernumber = $registration_id;
That will change the order number visible in your quickpay account to match the registration id of the transaction (for the primary attendee, if using MER) in EE.

I’ll put this change in the next version of EE. Thanks.


Runemester

November 23, 2012 at 7:49 am

Cheers Sidney – you just saved my day!
Thanks.
Viewing 2 reply threads

The support post ‘QuickPay not recording transaction/reg/payment ID’ 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 Runemester 12 years, 3 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server