susantau

Thanks for your reply! I went into phpmyadmin but realized that the problem is that the 3 tables don’t exist, and the instructions at that link you provided require selecting the tables that need repair, so I can’t do that since they don’t exist. So looks like my only choice is to perform a backup from a zipped Updraftplus in an external location… At least I have that.

thanks again

• This reply was modified 4 years, 1 month ago by susantau.
• This reply was modified 4 years, 1 month ago by susantau.

@aashik, My client went into PayPal and found that shipping calculator was “enabled” and set it to “disabled”. She had gone in there before looking but never found this feature, she had even talked with PayPal customer support. But your instructions were apparently what we needed. So then I recreated an order that PayPal had added the false amount to, but after the shipping calculator had been disabled, the extra charge did NOT get added. This very simple answer may be the solution, we are very excited about that and very grateful for your excellent, patient and proactive support.
Susan

So the owner of the Mana Pottery site (I am the webmaster) explained this problem in a Live Chat with PayPal support. PayPal responded by insisting the extra shipping charge is not getting added by PayPal, has nothing to do with PayPal, that this is coming from Woocommerce.

I really don’t see how this charge could be coming from Woocommerce. Woocommerce displays the order in checkout with the correct shipping and tax. But when you go to PayPal, in the displayed order there the shipping charge is suddenly $100 more. Then back in Woocommerce, the order gets flagged as “On Hold” because the order amount in PayPal did not agree with the order amount in Woocommerce. Really seems like PayPal is the weak link in the chain.

For now, I have added a note in checkout that warns customers purchasing by PayPal that they may see a false shipping charge added in the stage of the payment process when they go to PayPal and, if so, to report it to Mana Pottery who will refund the erroneous charge.

In other words, we still don’t have a solution – this is just the latest. ??

• This reply was modified 4 years, 2 months ago by susantau.
• This reply was modified 4 years, 2 months ago by susantau.

That makes total sense to me – all roads seem to lead to PayPal – and excellent point about a PayPal account that serves more than one purpose… I will pass this on to my client so she can scour her PayPal account for any shipping method/charge set up inside PayPal. If, no, WHEN we figure this out, I will report back here.
Thanks!

Hi @stuartduff, Thank you so much for your thoughtful and very helpful response. So I enabled debug logging in WooCommerce Shipping and Taxes and then I made a purchase that seemed to successfully replicate the problem. Woocommerce shows my order as On Hold, however, it appears that PayPal went ahead and charged me. The actual order with correct shipping and taxes comes to $17.36, but PayPal has charged me $117.36. Please let me know what you need from me to be able to look at the debug log. I immensely appreciate your help with locating and stopping this miscalculation.

thanks again!
Susan

I’m not the same person who requested this help, but I had the same question and your suggestion/code worked GREAT for me. THANK YOU!
(wildbluepixel.com)

• This reply was modified 4 years, 3 months ago by susantau.

So your restored backup is just resetting to some point in time when Woocommerce and Jetpack versions were still in conflict, so it makes sense you’ll get that error and restoring won’t help – unfortunately. If I were you, I would regain access to the admin dashboard again by temporarily changing the name of the Jetpack folder via FTP — but after you’re in, change that folder name BACK to the correct name and immediately update both the Jetpack and Woocommerce plugins before you log out again. That’s what I would do… I hope this helps!

@mellowvision Did you try removing and re-installing Jetpack? I believe that’s what I had to do…

@topboj) Glad to hear all is working now – thanks for replying.

I see this has been Resolved – but don’t see a conclusion in the above thread… Can we safely conclude that the problem was caused by a conflict between Jetpack and Woocommerce 4.4.0, and that this conflict was resolved with Woocommerce 4.4.1? But I’m still wondering if Braintree is safe to enable (per my last comment in this thread).

@topboj is your site still compromised?

That’s fantastic that you are picking this up! This has been one of my favorite themes – reliable and flexible. Thank you for caring for Simone!

• This reply was modified 4 years, 6 months ago by susantau.

@james,

My site is working with these new updates, but I had succeeded in getting my site working some days ago after I changed the name of JetPack via ftp, disabled Braintree, removed JetPack entirely then re-installed JetPack.

So yes, running JetPack 8.8.2 and Woocommerce 4.4.1 (plus a couple other brand new Woocommerce updates that rolled in yesterday), my site is still up – HOWEVER, I have NOT re-enabled Braintree – I’m concerned Braintree may have been conflicting with JetPack.

I’m curious if others are using the latest Woocommerce/Jetpack versions with Braintree enabled?

Is this the same Simone theme that was originally developed by Morten Rand-Hendrickson?

i changed the name of the jetpack’s plugin folder on the remote server via FTP and then I was able to log in. I tried a lot of things, but finally opted to remove Jetpack completely from the remote server via FTP. And then I installed and activated. The site seems to be working again. ONe thing I think is a possibility: maybe Jetpack got corrupted somehow because of a conflict with Braintree? One of the things I did before I re-installed/activated Jetpack was disable Braintree. I will be trying to get Braintree back running again later this week. If JetPack goes south again after Braintree is running, I will return here to report that to you.

Sorry, just now saw James’ question: Woocommerce 4.4.0.

• This reply was modified 4 years, 6 months ago by susantau.

Hi Gerroald,

Thanks so much for getting back and suggesting this final step. So I deactivated almost all my plugins (didn’t want to deactivate ManageWP Worker or I wouldn’t be able to get back into the site easily if locked out again) and…. I was able to log in! So you were correct about the problem being caused by some plugin conflict. Of course, the burning question is, which one??

So then I added the rest of the plugins back – in clumps – but even after re-activating the last clump of plugins, I was STILL able to log in – wha??? Oh – EXCEPT one thing was not QUITE the same as before: upon re-activation the Jetpack plugin required reconnection to WordPress.com, which I wavered about for a couple of minutes, and finally decided against because I never use anything in Jetpack AND I didn’t want to deal with WordPress.com. In fact I deleted JetPack altogether.

Because everything ELSE is back to how it had been and I can log in no problem again, I would suggest JetPack as a possible suspect.

Forgive me for not going those extra steps to really nail this conclusively.

At any rate, I am SO HAPPY to be able to log in properly to the site again. ??

Susan

• This reply was modified 5 years, 1 month ago by susantau.
• This reply was modified 5 years, 1 month ago by susantau.
• This reply was modified 5 years, 1 month ago by susantau.

Thanks for your reply. I actually commented on this in this other thread:
https://www.ads-software.com/support/topic/cap-on-overlapping-reservations/#post-12378982

thanks again