tmendes

Fixing it in the next plugin release is fine, thank you. It was causing problems but I already fixed it on our server.

No, we’re not using multisite. We have more than 41,000 users registered.

I disabled your plugin from sending the email (through the checkbox in administration), and I ended up having errors when users are registered, because the system still sends the email, but with empty subject, content and recipient.

The problem persists after the last upgrade. There are 8164 “wp_1_uwp_updater_batch_%” records in the wp_options table. Clicking the “taking a while?” link makes the page run for a few seconds before showing a “Allowed memory size of xxx bytes exhausted” error message.

No, thank you. I already made a few changes to the plugin’s source code to prevent the cron script from being created, and the admin message from appearing. I’m just letting you know so you can fix this bug, as other people might be experiencing the same problem.

I did that, but probably because it didn’t finish the first time it ran (due to the memory error I mentioned), it was automatically added again.

Not pending. The cron job was running, every 5 minutes, and causing the memory error I mentioned in my previous message.

The issues on our side also stopped on October 8th. We didn’t update anything either.

I believe it’s safe to remove the workaround, or at least leave it commented, so we can easily know if it happens again.

And apparently it was indeed something on PayPal’s side, but they’ll never admit that.

This is not related to WooCommerce’s upgrade. We didn’t upgrade it – still using 5.6.0.

I already posted PayPal’s return message related to the “failed with message ”” error.

The main problem is that we cannot reproduce, it’s totally random. But I’ll send you some information I was able to get from the requests made on our website.

What version of the Woocommerce Paypal Pro plugin are you currently running? We are on 2.9.7 but LINE 315 does not seem to be the appropriate place for the code & results to a critical error.

Sorry, I had added a few other lines to debug the problem, that’s why the line isn’t accurate. But I had added in a slightly different place than the developers did – I added right below the switch ( $parsedResponse[ 'ACK' ] ) { (between lines 306 and 307 of https://plugins.trac.www.ads-software.com/browser/woocommerce-paypal-pro-payment-gateway/trunk/woo-paypal-pro-gateway-class.php?rev=2611405).

Also, what exactly happens once a transaction encounters this error code (using the temporary fix provided)? Does the payment push through? Thanks!

The payment goes through anyway. The difference is that customers stop seeing the error, the order is set as complete/processing.

We had our first error on September 29. We’re using WP 5.8.1, WooCommerce 5.6.0 and WooCommerce PayPal Pro 2.9.7.

Paypal Credit Card Payment Failed with message: ”

We’ve also encountered this message. I started to log PayPal’s responses, and this is the error that they send when this happen:

cURL error 61: Unrecognized content encoding type. libcurl understands deflate, gzip content encodings.

No idea why. There’s nothing different on the orders where they send this as response. And again, the payments go through, despite the error message.

If it helps anyone, I added the following piece of code to my wp-content/plugins/woocommerce-paypal-pro-payment-gateway/woo-paypal-pro-gateway-class.php line 315:

// Check if Error Code is "10536" (duplicated invoice ID), if so set order as paid
if ( '10536' === $parsedResponse['L_ERRORCODE0'] ) {
    $this->transactionId = $parsedResponse[ 'CORRELATIONID' ];
    return true;
}

This is NOT meant to be a fix, just a workaround, while we wait for somebody to find the actual problem and come up with a real solution.

In our company we’re still investigating, and if we find anything, I’ll add it here.

So far, these are the characteristics to our specific problem:

* It happens a few times a day
* Most orders go through without problem, just a few have this problem
* The payment data is sent ONCE to PayPal, but it returns the message with the error code 10536 as a response for this first request
* The payment is processed, despite the error that they send

“No, allow multiple payments per invoice ID”

That’s exactly what we want to avoid. We do not want multiple payments per invoice ID, not even accidentally.

It’s weird because, as per my tests, the request is sent just like any other request, just once. But sometimes PayPal’s answer is the “duplicate invoice ID”, even thought they *just* processed the payment.

We’ve been seeing this message more and more – it started on September 29th, and it’s getting worse by the day. Among hundreds of orders, about 5 per day these last days, but yesterday we had 9.

Maybe something changed on PayPal’s side? We use WPEngine, I’m checking with them if something changed, but not a clue so far.

And we OBVIOUSLY don’t want clients to pay multiple times the same order. What we need is the order to actually change the status after the payment, which is not happening on those cases.

Just did!