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
PayPal IPN - failing to update payment status | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium PayPal IPN – failing to update payment status

PayPal IPN – failing to update payment status

Posted: January 13, 2013 at 7:55 am

Viewing 4 reply threads


Michael Koch

January 13, 2013 at 7:55 am

I am using Paypal IPN as payment gateway – everything seems to be configured well and my Event Espresso installation is receiving the IPN messages from Paypal (I can see this in the espresso/log-File: [ 2013-01-13 15:45:59 ] process_payments.php -> event_espresso_txn). However, the payment status of my attendees does not change …


Josh

January 14, 2013 at 9:37 am

Hi Michael,

Are you running the current version of Event Espresso? (as I type this, it’s 3.1.29.P.1) If so, can you check and verify that all the add-ons are up to date. The current version numbers of the add-ons are listed on the account page.

It may also help to install the simplified transactions page template:
http://staging.eventespresso.com/topic/problems-with-incomplete-payments-download/

Please be sure that the transactions page is published, not set to draft, private, or in the trash.


Michael Koch

January 14, 2013 at 2:47 pm

I am running the current version of EE, have all other plugin deactivated, and have installed the simplified transactions page template – and the transactions page is published …

But I just enabled the log file “paypal.ipn_results.log” (by creating the file – it did not exist before), and there I find the content:

[01/14/2013 10:44 PM] – FAIL: IPN Validation Failed . /cgi-bin/webscr : http://www.sandbox.paypal.com
IPN POST Vars from gateway:
=Abge9CZZ.aeOBH536SCHKErsCejKAhGkD7wnlkerNHlf-AZu2Wsi3Y2i,
IPN Response from gateway Server:
HTTP/1.0 302 Found^M
Location: https://www.sandbox.paypal.com^M
Server: BigIP^M
Connection: close^M
Content-Length: 0^M

Might that lead to the source of the problem?


Josh

January 14, 2013 at 3:06 pm

It doesn’t look like it’s connecting to your server. When you look at the sandbox debug output (it will display in a table with white text on a black background) what is the output there, (specifically URL’s)?


Michael Koch

January 14, 2013 at 3:19 pm

Just found the problem: cURL was not installed on my server – installing the package did the job …

Viewing 4 reply threads

The support post ‘PayPal IPN – failing to update payment status’ 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.

Event Espresso - Staging Server