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
Payment Pending for WorldPay Test Installation | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Payment Pending for WorldPay Test Installation

Payment Pending for WorldPay Test Installation

Posted: February 7, 2014 at 9:11 am

Viewing 6 reply threads


Andrew Dunn

February 7, 2014 at 9:11 am

Hello,

I’m having trouble getting WorldPay to update my Installation of Espresso with a Payment confirmed.

They just read ‘Pending’, the test client receives a successful receipt and I also (test merchant) receive a successful transaction.

Is this related to a Test installation. My Espresso logs don’t seem to have any errors and everytime I CHMOD the espresso/logs directory, it drops and becomes unwriteable after a registration.


Sidney Harrell

  • Support Staff

    •

February 7, 2014 at 5:31 pm

Make sure that you have gone through the steps ‘Enabling Payment Response’ in this document.


Andrew Dunn

February 10, 2014 at 6:07 am

Hi,

I’ve got the callbacks working – It was a index.html interfering with my redirect, using a Permalink solves this issue.

I have one question – if I cancel the test payment is still goes to the Payment Response URL I have set in WorldPay.

How do you recommenend we deal with this issue, use $_POST to detect success or failure? WorldPay only routes to one URL…


Andrew Dunn

February 10, 2014 at 6:10 am

Does it look like I need to alter my template to include something like:

http://stackoverflow.com/questions/8654126/php-worldpay-payment-response-example


Sidney Harrell

  • Support Staff

    •

February 10, 2014 at 3:31 pm

Currently, a cancelled transaction just maintains the ‘Incomplete’ payment status. If you want to give a special message, you could edit gateways/worldpay/worldpay_ipn.php (make a copy of the whole worldpay folder into uploads/espresso/gateways before making the modifications) and take a look at lines 26-30. Those correspond to the transaction status = ‘Y’ in that stackoverflow example. So you would edit line 30 to be:

}else if($_REQUEST['transStatus'] == "C") { ?>
            <strong>Transaction Cancelled</strong>
<?php }


Andrew Dunn

February 11, 2014 at 3:52 am

Hello

Thanks for this. I’ve gone with worldpay’s screens for now as I didn’t want to fuss about error handling.

Thanks


Dean

  • Support Staff

    •

February 11, 2014 at 4:15 am

Hi Andrew,

Do you still require further assistance with this?
Viewing 6 reply threads

The support post ‘Payment Pending for WorldPay Test Installation’ 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 Dean 11 years ago ago

Topic Tags

Tagged: , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server