Beret

Here is a screenshot of the resource usage my last release day: https://imgur.com/a/USwpZHY

There would be no point in whitelisting it if you dequeue it. You can either dequeue or whitelist.

So I should whitelist instead of dequeueing it because the dequeue gets reset everytime the theme updates?

As for the error message in the database, is that the full log entry, or do you have one where we can see the full stack trace?

This is just the normal woocommerce report. How would I access the full stack trace?

This is usually indicative of a conflict, either from your theme or another plugin.

Have you had a chance to test for conflict, as per https://docs.woocommerce.com/document/how-to-test-for-conflicts/ ?

The issue is this error only happens when I have a lot of people on my shop refreshing waiting for a drop and then a bunch of people trying to check out with the same product at the same exact time so it would be kind of hard to replicate.

I also had an issue where when people were checking out, the right side of the screen on the last step of the checkout, was greyed out. The part where you enter credentials such as CC or select PayPal. Has this ever happened to anyone?

@nitesh_singh But its not under the starter PRO? I have to pay $119 or $300 for this?

@rokasjan Hi sorry for late response. I added another test item, it should be seen there. I have international ordering setup.

@nixiack8 Hi sorry for late response. I added another test item, it should be seen there. I have international ordering setup.

@rokasjan Hi, I added a tshirt to the product page which should allow you to see the cart page

@nitesh_singh Thank you, I appreciate it.

@amandasjackson Any answer?

I have restored the problem items back and increased their stock from 0 to 1; however, the issue cannot seem to be replicated. https://hazybowls.com/shop/

• This reply was modified 5 years, 2 months ago by Beret.

@amandasjackson Yes they had issues with the inventory. They were set to 1. But nobody could ever check out with them so I had to pull them manually and set their stock to zero and sell them directly.

They were all duplicated from Hazy 50, and 52 from 51 and so on and so forth. But like I said, it just doesn’t make sense to me as all the other products were sold fine with no issue despite all being duplicated from the same source.

The only plugins that might have had an issue with it I believe are FlexShipping (i doubt it) and the WooCommerce Facebook plugin, which was outdated a few versions.

@amandasjackson So the last fatal error was Nov 12. My sale was Nov 24.

I however did have a wpdesk-sender prompt from Nov 22; however, nothing in the log for the 24th.

2019-11-22T22:54:23+00:00 DEBUG Sender payload: {“click_action”:”plugin_deactivation”,”plugin”:”flexible-shipping\/flexible-shipping.php”,”plugin_name”:”Flexible Shipping”,”reason”:”temporary_deactivation”,”variant_id”:0}
2019-11-22T22:54:26+00:00 DEBUG Sender response: {“headers”:[],”body”:””,”response”:{“code”:false,”message”:false},”cookies”:[],”http_response”:null}

What is interesting to me is why it was only those 3 items when they were duplicated from other product pages which sold just fine.

@amandasjackson Hi, yes, I thought that to be the case. Each item had a stock of 1.

However, even when I knew the three items in question WERE in stock, people were getting the error. Nobody was able to checkout despite the item being in stock. So I had to manually pull them from the store.

@rokasjan yes it is https://www.hazybowls.com/shop

Hello? They told me if DISABLE didn’t work, I should consult woocommerce support