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
Worldpay Update | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Worldpay Update

Worldpay Update

Posted: June 18, 2013 at 9:25 am

Viewing 1 reply thread


Andrew Mason

June 18, 2013 at 9:25 am

Hi,

Apologies if this has already been asked, I didn’t find anything when I searched.

Do I need to do anything about the updates announced on the Worldpay site? http://www.worldpay.com/support/index.php?page=domain-change&c=WW

I’m using EE version 3.1.30.7P

 

Andrew


Josh

June 18, 2013 at 11:55 am

Hi Andrew,

What this is basically saying is WorldPay is no longer allowing requests that go to IP Addresses instead of domain names. I checked and the Event Espresso WorldPay gateway uses the domain name specified for HTML form posts in the technical bulletin you linked to. It does not use IP addresses. So it should be good to go.
Viewing 1 reply thread

The support post ‘Worldpay Update’ 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, 8 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server