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 works. Sometimes (50:50) | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Paypal works. Sometimes (50:50)

Paypal works. Sometimes (50:50)

Posted: September 14, 2012 at 5:25 am

Viewing 7 reply threads


Chris

September 14, 2012 at 5:25 am

Hi there,

EE has made making money so much easier. Thank you for this great product. We enjoy it every day.

However one thing lets us scratch our heads each day and that’s a Paypal issue.

Everything is set up fine and works 50% of the time. Meaning, the whole process is operating as it should –
People attend to an event, use the Paypal payment option, IPN is obviously delivered. Attendee gets his ticket. Voila. No manual work needed any more. Perfect.

In the other 50 % , it is just the same as above with the exception that the process ends when payment via Paypal is made. We then get a message from Paypal that a payment was made and have to manually check into EE to adjust the payment information and send the ticket out.

The 50:50 thing happens within the same event and all other circumstances being equal (Except data of attendee of course)

Any idea on that?


Sidney Harrell

  • Support Staff

September 14, 2012 at 7:47 am

Hey Chris,
Can you check the wp-content/uploads/espresso/logs/espresso_log.txt file and see if the ipn messages are being received?


Chris

September 14, 2012 at 8:23 am

Hey Sidney,
just checked it and it proves:

Those transactions that ran smooth are well documented in the file.
Those that stopped cannot be found within.

So obviously some ipn messages get lost between Paypal and EE.

But why?


Chris

September 20, 2012 at 11:17 am

Ok, I fixed it myself via the EE Backend by

  • Removing Paypal ID
  • Saving
  • Reentering Paypal ID
  • Saving


Chris

September 26, 2012 at 2:24 am

Too happy too soon!

Again it does not work. Paypal’s IPN just does not reach Event Espresso although transaction is fulfilled.

So we still need help on this issue.


Chris

September 27, 2012 at 5:43 am

Additional hint:

Most times when people buy their ticket, this purchase creates a doublet of the data record in Event Espresso.

So one purchase – two identical records.

Might be helpful on this problem?


Sidney Harrell

  • Support Staff

September 27, 2012 at 10:56 am

Which version of EE are you on? 3.1.27.P had a fix for a problem with payments not getting recorded due to a problem with a sql query, whereas there was an earlier fix that dealt with EE not attempting to process the second IPN message if the first one is marked successfully. Paypal does send 2 IPN messages with each transaction, one while the customer is still on their site to EE’s Transactions page, and another one with the customer when they return to the Thank You page. You can get EE to record a lot more data by going to the general settings and turning on the “Full Logging” option. It will start recording every request that comes into the site, which may help in figuring out whether paypal didn’t send the ipn message, or whether EE had a problem processing it.


Chris

October 4, 2012 at 11:34 am

Hi Sidney,

thanks for detailed information. I’ve just activated the Full Logging. Let’s see what happens.

For the moment it remains strange. Today a client registered for two separate events with his very same credentials using Paypal as payment methode.

One booking went through as it should.
The other one again stop somewhere between Paypal and EE.

Viewing 7 reply threads

The support post ‘Paypal works. Sometimes (50:50)’ 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