Woocommerce: PayPal Intermittent `Transaction cancelled` or `Internal server error` on guest checkout

[hannahswain]

EXPLANATION OF THE ISSUE

Using WooCommerce 3.0.5 and guest checkout, there are three possible outcomes when clicking "Proceed to PayPal" from the checkout page:

1. PayPal payment options appear as expected

2. PayPal error:

Transaction Cancelled Error Message This function is temporarily unavailable. Please try your payment again later by returning to eBay and clicking the My eBay button.

1. Internal Server Error:

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log

Other known info:

• Same issue on Chrome and Firefox
• Enabling "create an account" on checkout makes no difference
• Works correctly if the customer is logged into the site
• No wp_debug errors
• PHP logs -> no mention of the issue

Related thread: https://wordpress.org/support/topic/transaction-cancelled/

Possible solution? https://en.forums.wordpress.com/topic/priority-paypal-error?replies=4#post-2941732

STEPS TO REPRODUCE THE ISSUE

1. Ensure PayPal Standard and Guest Checkout are enabled
2. Visit the shop as a guest, add a product to the cart and proceed to checkout
3. Click Proceed to PayPal
4. See either the PayPal payment screen, PayPal error or Internal Server Error

SYSTEM STATUS

`

WordPress Environment

Home URL: https://woobeta.mystagingwebsite.com
Site URL: https://woobeta.mystagingwebsite.com
WC Version: 3.0.5
Log Directory Writable: ✔
WP Version: 4.7.4
WP Multisite: –
WP Memory Limit: 256 MB
WP Debug Mode: –
WP Cron: ✔
Language: en_US

Server Environment

Server Info: nginx
PHP Version: 7.0.18
PHP Post Max Size: 100 MB
PHP Time Limit: 300
PHP Max Input Vars: 6144
cURL Version: 7.53.1
OpenSSL/1.0.1t

SUHOSIN Installed: –
Max Upload Size: 100 MB
Default Timezone is UTC: ✔
fsockopen/cURL: ✔
SoapClient: ✔
DOMDocument: ✔
GZip: ✔
Multibyte String: ✔
Remote Post: ✔
Remote Get: ✔

Database

WC Database Version: 3.0.5
WC Database Prefix: wp_
woocommerce_sessions: ✔
woocommerce_api_keys: ✔
woocommerce_attribute_taxonomies: ✔
woocommerce_downloadable_product_permissions: ✔
woocommerce_order_items: ✔
woocommerce_order_itemmeta: ✔
woocommerce_tax_rates: ✔
woocommerce_tax_rate_locations: ✔
woocommerce_shipping_zones: ✔
woocommerce_shipping_zone_locations: ✔
woocommerce_shipping_zone_methods: ✔
woocommerce_payment_tokens: ✔
woocommerce_payment_tokenmeta: ✔
MaxMind GeoIP Database: ✔

Security

Secure connection (HTTPS): ✔
Hide errors from visitors: ✔

Active Plugins (1)

WooCommerce: by Automattic – 3.0.5

Settings

API Enabled: ✔
Force SSL: ✔
Currency: EUR (€)
Currency Position: left
Thousand Separator: ,
Decimal Separator: .
Number of Decimals: 2
Taxonomies: Product Types: bundle (bundle)
external (external)
grouped (grouped)
photography (photography)
simple (simple)
subscription (subscription)
variable (variable)
variable subscription (variable-subscription)

Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)

WC Pages

Shop base: #4 - /shop/
Cart: #5 - /cart/
Checkout: #6 - /checkout/
My account: #7 - /my-account/

Theme

Name: Twenty Seventeen
Version: 1.2
Author URL: https://wordpress.org/
Child Theme: ❌ – If you're modifying WooCommerce on a parent theme you didn't build personally
then we recommend using a child theme. See: How to create a child theme

WooCommerce Support: ✔

Templates

Overrides: –
`

[mikejolley]

I've emailed PayPal since it appears to be a problem on the PayPal side. I'll reopen if they report back a problem with our request. You're cc'ed.

Thanks

[Bmorrical]

Same problem, was seeing this on 2.6.14, and updated to 3.0.5 with same problem. After redirection to Paypal, the following error:

[mikejolley]

Which shows it's a PayPal issue or an undocumented change. As I said, we have notified them.

[Bmorrical]

Thanks @mikejolley, full thread here from 16 hours ago talking about it too: https://wordpress.org/support/topic/transaction-cancelled/

Here is a fix I found in the comments of the previous URL:

This problem because woocommerce using url with website.com?cancel_order=true&order=order_number&order_id=160 and Paypal not support.

Solution:

1. Find and open file: wp-contentpluginswoocommerceincludesgatewayspaypalincludesclass-wc-gateway-paypal-request.php
2. find line

'cancel_return' => esc_url_raw( $order->get_cancel_order_url_raw() ),

Replace

'cancel_return' => urlencode( $order->get_cancel_order_url_raw() ),

[mikejolley]

@Bmorrical no it's not a fix. I can still replicate the issue after the change. Plus it wouldn't just start happening overnight - that code has been in place for months.

[AlanSChin]

Before I attempt changing the code, any more comments on the "fix" working or not? I have this problem too.

[Bmorrical]

Hi @AlanSChin, the fix worked perfectly for me, and dozens more on that forum link above. I suspect Woo/PayPal will work out a fix/patch for this. But it's quick fix to get my store back online and working again. Cheers!

[starlajay]

Hey it worked! Thanks Bmorrical! Though would this break the cart if I did another update? For now it works, I can't have my client lose any more business.

[Chris-Anne2]

This worked for me. Thank you so much!
Chris-Anne

[mikejolley]

On sandbox, after the change:

• Checkout as guest
• On paypal choose pay with cart/checkout as guest
• Use browser back button to woocommerce
• Checkout again
• See 500 error.

I think this changes nothing - it's fairly random in occurrence.

[starlajay]

Updated to 3.0.6, error still occurs.

[dcpotter22]

@Bmorrical saved the day for me, my brother and sister make and sell craft chocolates, final big push for sales today and tomorrow for shipments to arrive in time for Mother's Day, and then that error popped up. I updated from 2.6 to the latest woocommerce, still had the issue. That was the extent of my abilities and the cursing began. Finding this thread and replacing that line of code solved the issue it seems, hopefully it works for customers through Thursday, thanks so much!

[ciyonn]

@Bmorrical Hello Where Do I Fine The Files wp-contentpluginswoocommerceincludesgatewayspaypalincludesclass-wc-gateway-paypal-request.php ? Just Starting Out And My Store Paypal Not Working ?

[fox-didl]

@Bmorrical: It seems just to work in one direction. If the customer is clicking on "cancel" on paypal site, it's not going back on the shop. Just getting this:
"Not Found

The requested URL /webapps/https://xxxxxx.shop/warenkorb/?cancel_order=true&order=wc_order_591243524f900&order_id=14153&redirect&_wpnonce=0062c7d855 was not found on this server."

[siriusmw]

Also happening on all of our sites since WooCommerce upgrade.

[mingjuitsai]

@Bmorrical the code didn't work for me.. I am on WooCommerce 3.0.6

[Bmorrical]

Sorry all, I am not the developer. I just passed along a little code that I found that helped me, maybe it would help you. I've been tracking this issue across a couple forums and it's a pretty big issue and I'd guess that WooCommerce is doing what they can to fix it as soon as possible.

[ryanstockau]

After doing a bunch of testing, I was able to fix this on my system by running the $redirect variable of WC_Abstract_Order::get_cancel_order_url_raw() through esc_url_raw(). Not sure if this will apply to everyone or not, but it's worth mentioning.

return apply_filters( 'woocommerce_get_cancel_order_url_raw', add_query_arg( array( 'paypal_cancel_order' => 'true', 'order' => $order->order_key, 'order_id' => $order->id, 'redirect' => esc_url_raw($redirect), ), $cancel_endpoint ) );

To me it looks like Paypal can't handle the redirect variable being an unencoded URL anymore. So it's not the full cancel_return URL mentioned above that's the problem, it's just the redirect portion of it. I figured it out by removing parts of the query string that gets sent to Paypal, and eventually after removing the redirect section it started working.

[ciyonn]

So Where Do I Go To Apply The Changes?

On Tue, May 9, 2017 at 10:44 PM, Ryan Stock [e-mail]
wrote:

After doing a bunch of testing, I was able to fix this on my system by
running the $redirect variable of WC_Abstract_Order::get_cancel_
order_url_raw() through esc_url_raw(). Not sure if this will apply to
everyone or not, but it's worth mentioning.

return apply_filters( 'woocommerce_get_cancel_order_url_raw',
add_query_arg( array( 'paypal_cancel_order' => 'true', 'order' =>
$order->order_key, 'order_id' => $order->id, 'redirect' =>
esc_url_raw($redirect), ), $cancel_endpoint ) );

To me it looks like Paypal can't handle the redirect variable being an
unencoded URL anymore. So it's not the full cancel_return URL mentioned
above that's the problem, it's just the redirect portion of it. I figured
it out by removing parts of the query string that gets sent to Paypal, and
eventually after removing the 'redirect' section it started working.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/woocommerce/woocommerce/issues/14956#issuecomment-300365490,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbQUSVKkLesUjKDgdIOfW8MELe8VtrIXks5r4TKrgaJpZM4NVL2S
.

--

IYON of TEAM JON DOE
[email protected] [e-mail]
teamjondoe.com http://teamjondoe.com

[phone]

[jondaley]

I was getting this error on 2.6.14, and thought I'd upgrade to see if that fixed it. No such luck.
And the cancel_return line didn't fix anything (as you might guess, since that variable is only used when cancelling the order...)

I'll have to try out the redirect theory.

[galbaras]

It looks like the respective code in class-wc-gateway-paypal.php hasn't been changed in a while, and 2.6.14 "developed" it suddenly, so this really looks like a PayPal issue, especially since it only happens some of the time, which implies that some PayPal servers have the problem, but not others.

[jondaley]

I've made the change to class-wc-order.php for the redirect, and it at least doesn't break the cancel url, so it is at least that going for it. But, since the problem appears to be random, I can't confirm that it is fixed yet.

galbaras: your some paypal servers theory is a good one.

I have a support phone call with paypal in the morning, so we will see what they say.

[siriusmw]

Any chance this is related to TLS1.2 changes at PayPal?

[salehwvss]

Hello the problem appears to be with certain browsers like google chrome. I get the following error with Chrome:"This function is temporarily unavailable. Please try your payment again later by returning to eBay and clicking the My eBay button."

But the problem does not occur with Microsoft Edge.

[siriusmw]

I just received a failure report from an Edge user. (We're running dozens of sites that are reporting issues, and don't see any consistency yet .)

[galbaras]

Can everybody please contact PayPal? If there's enough pressure on them, they may actually check the situation, rather than resorting to finger pointing.

Also, if everyone can post whether this is related to SSL, that may help isolate the TLS angle.

[jondaley]

Not SSL. I don't see it as a browser specific issue either. I haven't yet seen a failure on google chrome myself.

[macaudio303]

Had the same issue on 2 sites. On both I replaced:

'cancel_return' => esc_url_raw( $order->get_cancel_order_url_raw() ),

with

'cancel_return' => urlencode( $order->get_cancel_order_url_raw() ),

...and it worked... or at least seems to work so far, but some of you say it's intermittent. I only use firefox and will try other browsers tomorrow. Anyone have an idea when this started. I noticed a drop in orders the last 2 days.

[fox-didl]

@ryanstockau: Where do I add this update?

[ryanstockau]

@fox-didl I added it in a custom class that overrides the WooCommerce class, but for others I think it should be in wp-content/plugins/woocommerce/includes/abstracts/abstract-wc-orders.php, near line 2187. Keep in mind that updating WooCommerce will break this, but hopefully by that point the issue would be fixed...

[progressive01]

Applied fix above as Paypal sent me this ....
"Here’s the information the merchants have given to us and said it fixed the problem with their website. We hope that helps.
This problem because woocommerce using url with http://website.com?cancel_order=true&order=order_number... and Paypal not support.
Solution:
Find and open file: wp-contentpluginswoocommerceincludesgatewayspaypalincludesclass-wc-gateway-paypal-request.php

find line 'cancel_return' => esc_url_raw( $order->get_cancel_order_url_raw() ),

Replace 'cancel_return' => urlencode( $order->get_cancel_order_url_raw() ), " Close quote.

Taken from this thread. It has fixed it for now, but watching closely.

[siriusmw]

From PayPal? GREAT! Does this mean it is related to security and the upcoming changes? (Other software is having similar issues.)

[mtrenord]

Thanks for the fix, working for me! I'd hate to think how many transactions were lost as a result.

[mikejolley]

Comment blindness.

See https://github.com/woocommerce/woocommerce/issues/14956#issuecomment-300287651

Also note that changing that line breaks the 'cancel' link from PayPal back to your store. We're in contact with PayPal so they are looking into it.

[galbaras]

A more sustainable way would be to write a filter in functions.php.

add_filter( 'woocommerce_paypal_args', 'woo_override_cancel_url', 2 );
function woo_override_cancel_url( $args, $order ) {
    $args['cancel_return'] = urlencode( $order->get_cancel_order_url_raw() );
    return $args;
}

Can someone please test this?

[DGStefan]

@galbaras
Your snippet is not working since you set the priority to 2 and not the number of arguments that should be passed. The correct filter should be.

add_filter( 'woocommerce_paypal_args', 'woo_override_cancel_url', 10, 2 );
function woo_override_cancel_url( $args, $order ) {
    $args['cancel_return'] = urlencode( $order->get_cancel_order_url_raw() );
    return $args;
}

[mikejolley]

The correct workaround is just to remove cancel return completely. The URL you're both passing is wrong. As I stated above.

This is what I've just sent to PayPal:

Right; using production on any WC store and checking out should let you see the problem right away.

I’ve indeed narrowed it down to cancel_return. This is the URL we’re sending from our side:

cancel_return=http%3A%2F%2Flocal.wordpress.dev%2Fcart%2F%3Fcancel_order%3Dtrue%26order%3Dwc_order_5912433879d52%26order_id%3D130%26redirect%26_wpnonce%3D6fe191e872

Notice how this is encoded - %26 is an encoded ampersand.

I noticed that removing the query string portion of this URL worked around the issue. Removing the %26order_id%3D130 part also worked around, but the cancel URL on the PayPal page does not include any part of the query string after the ampersand, so it looks like this on your site: 

http://local.wordpress.dev/cart?cancel_order=true

Notice it stops at the ampersand?

It looks like the change your side could be that these are being decoded before splitting the params.

I’m guessing the error is then because PayPal sees order_id and tries to do something with just that, rather than seeing the entire string as the cancel_return URL.

This is not fixable our side unless we stop using cancel_return completely - we need the query string. I also worry other URLs (image URL, return URL, IPN URL) would also break in the same way now, or the future, if this logic is rolled out everywhere.

Thanks

[AdminFlexo]

@mikejolley ... I'm not a developer so, does it mean we have to wait for PP and can't really fix it our end?
thanks,
R

[bencoates]

@AdminFlexo - kinda correct. The error is on PayPal's side as it's incorrectly interpreting the URL that Woo passes to PayPal. The fix described by @DGStefan does work, we've just tested it, so you will at least be able to process transactions, but it could result in some errors if customers decide to bail out of a transaction, as I understand it. Someone will correct me if I'm wrong, but at least we can now process payments successfully.

[ryanstockau]

@bencoates Does my fix above not solve the issue while still allowing you to have a correct cancel link? Unless it's only solved it in my situation.

[petermelden]

I called PayPal and explained everything. They simply referred to Stackoverflow and paypal-techsupport.com because they are unable to see any issues with my account...

Already lost a few hundred dollars :-1:

[bencoates]

@ryanstockau I'm living in hope that this will be resolved quickly enough so that we don't have to worry about the cancel link. It's hardly used on any of our client sites and we can deal with the complaints as and when they arise. But watching it closely, and in the meantime the suggestion using the filters seems to be working well.

[jwbrothers]

I am interested in a resolution as well.

[fox-didl]

@mikejolley. I followed your answer and deleted the complete line of cancel return. It's not nice - ok - but working in a kind of unprofessional way. The important part: customers can buy again and this is good. OK they can't go back by clicking a link - this is really not nice, but ok in this situation.

[rivaflush]

Also seeing this issue. Very frustrating.

[dangcv]

Hi All,

I created new simple plugin fixed this problem. I tested and using on my site (live). I hope can help more shop.

https://github.com/dangcv/fix_woocommerce_paypal

[mitch827]

same problem here, definitely not a problem only on paypal side.

[rivaflush]

I just tried the plugin and it works great thanks @dangcv

[im-emmash]

I installed the plug-in but no difference on my side :(
We try other browsers and clear the cache... sometimes, we get the error Transaction cancelled, sometimes it's Your cart is empty and sometimes it's something else... and sometimes it works (rarely)... no logic at all!
And Paypal keep saying that's everything is working fine on their side... grrr!

[tjl666]

Yes, we're having this issue too, not sure why this ticket is closed when it's clearly still occurring? It seems very sporadic for us, sometimes it hits the error, sometimes it doesn't and there seems to be no clear pattern at all. The only changes we have made recently is updating WooCommerce so this must be a WooCommerce issue?

[im-emmash]

@tjl666 ... On our side, we use WooCommerce 2.6.14 so no recent update and same problem since sunday or monday of this week... I really think it's a Paypal issue...!

[tjl666]

Ahh ok @im-emmash that makes sense. Annoying PayPal are saying everything is fine their end though, makes it so frustrating in terms of reaching a fix, especially when it's affecting client sales - arghh!!

[wpww]

@dangcv installed the plugin and worked great for me on live site. Thanks so much!

[jondaley]

@im-emmash: that is interesting about your failure with the plugin. I just looked at the code, and it looks good, and if that doesn't stop the problem, then all of the theories about encoding the URL aren't correct, because the base64encode should do a good job to avoid all of these potential issues.

(@dangcv I do wonder if there is a security/XSS issue with this new plugin - I'll bet I can make your site redirect to another website by passing in a custom base64 encoded URL. Probably should make sure that it is a relative to the site, or uses the correct domain or something to avoid outside links.

And maybe even parse it better than that, by checking out the parameters, etc.)

[mensmaximus]

Just a side note. Paypal is trying to get rid of the old paypal interface since years and tried to move customers to paypal checkout, paypal pro and paypal plus. None of my customers has any issue with those three only with the old standard gateway.

[im-emmash]

@mensmaximus Well... if it still occuring, they will instantly get rid of us...!

[iruy]

@dangcv fix worked for me! Thank you

[AlanSChin]

I installed the plug-in and it seems to be working.

[gwegner]

@mensmaximus that's what I'm thinking too. They hired sales guyes that are calling me since months trying to convince me to switch to Paypal Plus. I didn't want. But now that I'm experiencing massive amounts of cancelled transactions what really costs me money, I've finally bought the Plus plugin and made the switch. So they got what they wanted. But this really sucks. I can only hope that it was not intentional and that they will fix the old interface. It's the problem with those strong dependencies on few big players.

[Thonk-Steve]

Hi Just to confirm that this is happening to me with Woocomm Version 2.6.14 also.

I'm not able to upgrade to version 3 yet due to problems with grouped products that aren't fixed yet. So I do hope you'll be rolling back a fix or Version 2.6.14 also?

[jondaley]

@dangcv the plugin appears to be working for me as well. (four orders came in).

I'll look into security issues now.

PS. We talked to Paypal yesterday and they admitted the problem was on their end, but then they were supposed to call back this morning, and they didn't...

[Chunkford]

WOW, @mikejolley thought I would let you know I just got off the phone with someone at Paypal, and they point blank told me that it is Woocommerce at fault here and that you have held your hands up and admitted it.
Still trying to work out how it's your fault when I haven't changed a single thing on my production site, but yet all of a sudden Paypal isn't working!
I think someone needs to nip this in the butt pretty sharpish if this is what Paypal is telling everyone.

[dangcv]

@jondaley, I fixed security issues.

@AlanSChin, @im-emmash you can create new order and check.

[jondaley]

@Thonk-Steve have you tried the dangcv's plugin? I've looked it over, and I believe it will work fine for 2.6.14 as well as 3.0.

[ciyonn]

@dangcv where do i get the plugin?

On Wed, May 10, 2017 at 10:45 AM, Jon Daley [e-mail]
wrote:

@Thonk-Steve https://github.com/Thonk-Steve have you tried the dangcv's
plugin? I've looked it over, and I believe it will work fine for 2.6.14 as
well as 3.0.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/woocommerce/woocommerce/issues/14956#issuecomment-300524897,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbQUSWKqElQ4uVfByaqxoUPjflNc3-6eks5r4duigaJpZM4NVL2S
.

--

IYON of TEAM JON DOE
[email protected] [e-mail]
teamjondoe.com http://teamjondoe.com

[phone]

[jondaley]

@dangcv much nicer. I believe that fixes the major issue at least. I wonder if it should be checked a little further - ie. so the URL can't be set to delete a post or something? Though I think maybe default wordpress checks a nonce or something to prevent actions from coming from outside. Perhaps poorly written plugins could still be hacked?

Maybe the "/cart" or "/cart/cancel_order..." could be checked as well? (though maybe that is a customizable value?) I don't know how much is a real issue, and how much is just me being paranoid.

@ciyonn: there is a link above, but here it is:
https://raw.githubusercontent.com/dangcv/fix_woocommerce_paypal/master/fix_woocommerce_paypal.php
You just need the one file, and you can put it in wp-content/plugins/ or make a new directory for it inside of plugins.

[ciyonn]

@dangcv
http://t.sidekickopen68.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg2BW4yMW5w6M-g65365MW2zq3QW56dTp7f6vFwtz02?t=https%3A%2F%2Fgithub.com%2Fdangcv&si=6272099735306240&pi=9df032cc-558c-471f-e2b9-353bb1e4e547
thank
you got it

On Wed, May 10, 2017 at 10:50 AM, Jon Daley [e-mail]
wrote:

@dangcv https://github.com/dangcv much nicer. I believe that fixes the
major issue at least. I wonder if it should be checked a little further -
ie. so the URL can't be set to delete a post or something? Though I think
maybe default wordpress checks a nonce or something to prevent actions from
coming from outside. Perhaps poorly written plugins could still be hacked?

Maybe the "/cart" or "/cart/cancel_order..." could be checked as well?
(though maybe that is a customizable value?) I don't know how much is a
real issue, and how much is just me being paranoid.

@ciyonn https://github.com/ciyonn: there is a link above, but here it
is:
https://github.com/dangcv/fix_woocommerce_paypal/blob/
master/fix_woocommerce_paypal.php

You just need the one file, and you can put it in wp-content/plugins/ or
make a new directory for it inside of plugins.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/woocommerce/woocommerce/issues/14956#issuecomment-300526560,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbQUSfER2d3WmH1B5U07KOgpdbUP4tfNks5r4dzHgaJpZM4NVL2S
.

--

IYON of TEAM JON DOE
[email protected] [e-mail]
teamjondoe.com http://teamjondoe.com

[phone]

[FrankASW]

Paypal said Worpress is making updates
So to know the update times, you need to get in touch with WP staff. Will it be true?

[mikejolley]

No. PayPal are looking into this - they have acknowledged the issue and are working on it. We'll update you all when we hear back.

[jondaley]

No. At best it would be woocommerce, not wordpress. I wish paypal would publish their changelog when they make changes, so developers have time to fix their code.

[siriusmw]

Exactly! Especially since they appear to roll them out sporadically over servers. Will the patch above uphold through TLS 1.2 and remain compliant? Closing holes while passing data was a big issue that was addressed.

[plumcitypaint]

can someone tel me exactly where to insert this code? i'm not a programmer but have inserted code before if I can get an exact location. i need this fix ASAP please @dangcv

[lingx3721]

@plumcitypaint Here, /wp-content/plugins/woocommerce/includes/gateways/paypal/includes/class-wc-gateway-paypal-request.php
Line 89

[dangcv]

Install

1. Download file https://github.com/dangcv/fix_woocommerce_paypal/blob/master/fix_woocommerce_paypal.php

1. Upload to folder wp-content/plugins

2. Go to admin page > plugins and active

[jondaley]

@siriusmw This fix has nothing to do with SSL, so if TLS1.2 breaks something, it will be a different error. :)

To install, follow @dangcv's advice - you don't need to modify the woocommerce code directly. The next time woocommerce is upgraded, hopefully, they will make it so dangcv's code is no longer needed...

Though, dangcv, I would use this URL, so then people unfamiliar with github don't need to find the "raw" button.

https://raw.githubusercontent.com/dangcv/fix_woocommerce_paypal/master/fix_woocommerce_paypal.php

[plumcitypaint]

@dangcv this worked, virtual high fives!

[novativmedias]

Hi Guys! Am I the only one here who prefers to wait for WooCommerce update/fix instead of playing in the code? The site that I'm having trouble with doesn't have child theme so I'm not really for the idea of playing with the code or installing a plugin that I don't know about. Also, it seems to have a lot of different "version" of the problem... Am I right to wait or am I totally wrong ? Thanks all ;)

[siriusmw]

Nope, I'm not risking it. Don't have time to babysit it, and i's too close to big changes due by June 1.

[mikejolley]

@Chunkford we can't fix this really - we can remove the cancel_return arg but that doesn't fix older versions (2.6.x), and we kinda need it. We need to wait for PayPal. I'm not happy their support is saying this because:

Looks like this is not just Woo commerce but another partner is reporting this as well, so something on our end itself. Its been filed as a big priority issue and being looked at. Will provide updates as soon as I hear back from team here.

[Chunkford]

@mikejolley you shouldn't have to fix anything buddy, it's 100% Paypal.
I was just shocked and nearly fell off my seat when a member of the 'website support staff' (in the UK) told me point blank it was Woocommerce and not theirs, even after I pointed out the reasons why it's not.
I gave up trying to tell him in the end but thought you might want to know as that's not what they should be saying.

[FrankASW]

@dangcv thanks

[im-emmash]

If everyone would be calling at 1-888-215-5506 (Paypal merchant solutions tech service) mentionning this problem... I think it should help us! Go! ;-)

[jondaley]

@novativmedias the plugin is pretty simple, as far as plugins go. I'd be willing to bet you have far more scary plugins installed on your site already. Based on how quickly dangcv fixed the problem I mentioned, I'm guessing he's a decent coder, and I realize this doesn't really mean anything, but I have 30 years of software development under my belt, and this plugin receives my stamp of approval, which I wouldn't say goes for most plugins (including the original woocommerce plugin).

If you are losing orders, then there isn't much to risk by installing this tiny plugin. But, if you don't mind not getting orders paid for until woocommerce can update their plugin to work with the new paypal (or maybe paypal will revert their changes? Seems unlikely, particularly since you get a different answer depending on which tech support person you talk to), then it is certainly easiest to wait.

[novativmedias]

@jondaley Many thanks for your opinion. I've seen a lot of different plugins in the thread. Which one receives your approval's stamp plz? I'll try it. I begin to think the FIX will not be done today by any of the PayPal or WooCommerce teams.

[mikejolley]

Our team has made a few changes on their end and wanted me to check with you to see if you are seeing the same issue still happening. Can you please confirm?

PayPal have added some fixes their side. This appears to have resolved it and the cancel URL works as it should without changes.

[Thonk-Steve]

@mikejolley will their fixes also help woo 2.6.x sites?

[mikejolley]

@Thonk-Steve Yes because our integration requires no changes.

[novativmedias]

OH! Seems to work over here! Paypal standard but not Paypal Express Checkout... May be I have to reconfigure API Credentials. I'll troubleshoot a bit more.

[Thonk-Steve]

@mikejolley thanks for confirmation 👍

[Chunkford]

@mikejolley Just tested and it seems to be working.
Will make a few more over time just to be sure but positive so far.
Thanks for badgering them on our behalf

[macaudio303]

called to badger them myself and saw this when on the phone. Thanks @mikejolley for the help!

[sovitranjitkar]

@mikejolley Issue seems resolved now thanks for addressing it.
Also thanks for @dangcv for your simple but really helpful plugin.
Seems like in a short time it landed to the moon safely and retired with respect and dignity :)

[starlajay]

@mikejolley thank you so much it works!

[mensmaximus]

Sidenote: Just experienced paypal issues with fleurop flower shop and they use a shop on windows iis (aspx pages) not woocommerce.

[siriusmw]

We are experiencing it elsewhere as well. Is it impossible that it is related to the TLS1.2 changes, since special characters are being addressed; and the run above stops at ampersand? We are due for full changeover on June 1, and PayPal seems to upgrade sporadically across servers. The timing seems relevant. (And if that's the case, can we escape offending characters?) From "not a programmer. obviously."

[yosauce]

I am having this same issue. Was a fix discovered?

[dangcv]

This problem of PayPal, I think PayPal fixed long time ago.

Vào Th 6, 22 thg 3, 2019 vào lúc 11:14 yosauce [e-mail]
đã viết:

I am having this same issue. Was a fix discovered?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/woocommerce/woocommerce/issues/14956#issuecomment-475488265,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbRg6Lr7JYntHhzkGGU_GLwS87QIhTf5ks5vZFi0gaJpZM4NVL2S
.