|
Todd
|
September 21, 2012 at 12:03 am
Hey there,
We’ve got our EE installation running fairly well, except for one [major] glitch. We’re using PayPal Pro to process transactions, but the transactions are all showing as completed in the PayPal Sandbox, but as incomplete in the EE admin area.
I have searched around the forums for awhile now, followed the steps in this post, but to no avail. Our current setup is WP 3.4.2 with EE 3.1.26P. I’ve seen so many threads with PayPal issues that I really doubt we’ll have any luck getting this sorted, but any help is appreciated.
Other things to note, the /wp-content/uploads/espresso/logs folder has permissions set to 777, but no ipn log is showing up. The espresso_log.txt file is there, but that’s it. We have no custom payment gateway files in /uploads/espresso/gateways/. We also have the stripped down txnpage.php template in use for our transactions template. Our PayPal settings has IPN enabled and pointed at ourdomain.com/transactions/. The transactions page is publicly visible. We have a private SSL certificate and we’re using the EE SSL/HTTPS plugin to force SSL on the Events page, Transactions, and the Thank You page.
Thanks for any help, homeys!
|
|
Seth Shoultes
|
September 21, 2012 at 12:22 am
@Todd sometimes the PayPal sandbox doesn’t work right (I spent hours/days/weeks finding this out). You might want to try a live payment to see if that works.
Other things to try:
- Try setting the /wp-content/uploads/espresso/logs folder permissions to 755. The 777 vs 755 varies between hosts. Because of their security limitations, they will only allow you to use one or the other.
- Make sure CURL is enabled on the server.
- Try deactivating the Event Espresso SSL/HTTPS plugin and use the WordPress HTTPS/SSL plugin instead. Ours was basically a branch of an earlier version (2.0) of that plugin, because they broke something after the 3.0 update. It literally borked thousands of sites that required SSL.
Hope that helps!
|
|
Sidney Harrell
|
September 21, 2012 at 12:38 am
Also, upgrade to 3.1.27.P. It has a bug fix dealing with recording payment status in the db.
|
|
Todd
|
September 21, 2012 at 2:34 pm
@Sidney Harrel after upgrading to 3.1.27.P every transaction I attempt to process with PayPal Pro returns a 10001 Internal Error code. I also tested with Stripe, which does work. I reset my PayPal API Credentials and entered in the new info and tested again, but still no dice.
Actually, if I attempt a live payment, I get a 10002 Security Error. Note that I have a valid private SSL certificate.
|
|
Sidney Harrell
|
September 25, 2012 at 10:39 am
PayPal’s documentation for their error code 10002 states: “This error can be caused by an incorrect API username, an incorrect API password, or an invalid API signature. Make sure that all three of these values are correct. For your security, PayPal does not report exactly which of these three values might be in error.”
Make sure that when you turn on the sandbox mode, you switch all the credentials to those of a sandbox account. Paypal’s sandbox is a completely different system / server than the live system, and accounts on one will not work on the other.
Another thing to check for is a trailing space on any of the credentials, which is common when copy and pasting
If you are still having problems, send us wp-admin login credentials, and we can put our sandbox credentials in and run some tests.
|
|
Todd
|
September 25, 2012 at 11:37 am
I was able to get it working. Although since we’re in Canada and our client wants AMEX processing, we’ve moved to Stripe. \o/
|
|
Viktor Ovcharenko
|
October 2, 2012 at 6:49 am
Error Code: 10501
Short Message: Invalid Configuration
Short Message: This transaction cannot be processed due to an invalid merchant configuration.
Severity Code: Error how to solve
|
|
Josh
|
October 2, 2012 at 9:39 am
Hi Viktor,
Is this a confirmed PayPal Pro account where the billing agreement is active?
https://cms.paypal.com/us/cgi-bin/?cmd=_render-content&content_ID=developer/e_howto_api_nvp_errorcodes
|
