stepfaul

I am running WC 3.0.5 and have just tested paying by PayPal and received the ‘transaction cancelled page’ upon the very first attempt at trying to pay. This is really worrying as I wonder how long this has been going on for??

We also take Stripe and Amazon Pay so the impact on our sales would have been reduced as PayPal is not our most popular payment method.

I just changed the code as suggested earlier in this thread, and three checkouts in a row have successfully displayed the correct PayPal sign in page so it looks like the workaround has worked. I will continue testing.

EDIT: After reading that I should watch out for incorrect amounts after applying the workaround I have now disabled PayPal. Not worth taking the risk in potential loss of sales. I will wait for a permanent fix.

After reverting the code back to the original code PayPal just worked for me so the problem is indeed intermittent for me as well.

Steve.

• This reply was modified 7 years, 10 months ago by stepfaul.

Try using this website to identify the culprit(s) – https://www.whynopadlock.com/

Sounds like you have resource using http rather than https on that page.

Sorry to hear of your bad experiences. In their defence I have raised a number of tickets over the years with one ticket raised and closed a week or so ago and support has been great every time for me. There have been delays in ticket responses sometimes, but overall I have been impressed. Paid plug-ins aside remember that WooCommerce itself is free.

I have learnt from experience to always test updates on my staging site first and also to delay WooCommerce plug-in updates until a few version revisions after a major update. This approach has worked for me so far, maybe I have been lucky, who knows…

I would imagine support are really struggling at the moment in some areas as the last update was a pretty big one technically and obviously broke some sites in the process. Some users seem to have gone and updated their live sites without any testing and then been surprised when something has broken (I am not for one minute stating that this has happened in your cases).

For the record I am in no way connected to WooCommerce at all.

Steve.

Hi Mike,

Thanks for the response. I get a 404 error when following the above link…

Steve.

Thank you Thomas

Great news, thanks to you and Mike for the quick response on this.

Thanks Mike, I would appreciate that.

I have contacted WooThemes and opened up a support ticket. I should have checked the guidelines on this forum as it states to do that if the plug-in is a premium one.

Personally, I am not able to code myself but as I have paid good money for this plug-in I will await the response from WooThemes. I am running an up to date version of Canvas which is also a WooThemes product so I was hoping Canvas, WooCommerce and WooCommerce search would all play together quite happily.

I have a slightly older version installed on a staging site and the search also broke after the upgrade to WooCommerce 2.6. Stupidly I thought this would not happen on my live site as there were some differences between the two :-(. That will teach me a lesson.

Steve.

Disabling the plug-in fixes the search from with WooCommerce admin page and also the filtering. Obviously the search box gets removed after disabling though ??

Thanks for taking the time to respond, that css has done the job perfectly.

Steve.