Products not adding to store and cart

I was able to update the stock via quick edit just now, and it’s showing as in stock. However, it’s still showing Read more on the shop page, after I’ve cached the site and disabled my caching plugin,

Hi @nicolenoppe ,

I was able to update the stock via quick edit just now

Awesome, that is one step closer!

The product is still displaying as “this product is currently out of stock and unavailable” on my end. https://snipboard.io/zDZebv.jpg

Since we have run through a few troubleshooting options, could you delete the product, clear your cache once again, and try to add the product as new?

Let me know the results!

It still doesn’t want me to publish a new product. It just saves it as a draft.

Hello @nicolenoppe!

I was able to update the stock via quick edit just now, and it’s showing as in stock. However, it’s still showing Read more on the shop page, after I’ve cached the site and disabled my caching plugin

I can confirm what @roxannestoltz is seeing from my side and to add to what was said, make sure to test these recommendations (creating the product as new or re-saving it) while still being in conflict-test mode as pointed out above.

It has been noted that plugins might interfere with a product’s data from being retained or stored properly.

Please let us know how it turns out!

I have my site in troubleshooting mode using the plugin (Health Check & Troubleshooting). With all the plugins disables, only Woocommerce active, the new product doesn’t want to publish.

Hi @nicolenoppe ,

Please could you go ahead and contact your host and ask them to make sure that your cart and checkout pages are excluded from being cached, and see if there is any difference?

Please let us know how this goes!

Okay will do, thanks!

Hello,

I’ve been in contact with my host’s support team, and they only responded that they’ve cleared the server’s cache. They’ve also responded with the following:

Further, the error logs shows the below error.
> ==
> [27-May-2022 15:10:12 UTC] The
> Automattic\WooCommerce\Admin\API\Options::get_options function is
> deprecated since version 3.1.
> [27-May-2022 15:10:12 UTC] The
> Automattic\WooCommerce\Admin\API\Options::get_options function is
> deprecated since version 3.1.

Hi @nicolenoppe ,

Thanks for the update!

I’ve been in contact with my host’s support team, and they only responded that they’ve cleared the server’s cache.

Has this made any noticeable difference from your end with regard to the issues experienced with your products?

Further, the error logs shows the below error.
> ==
> [27-May-2022 15:10:12 UTC] The
> Automattic\WooCommerce\Admin\API\Options::get_options function is
> deprecated since version 3.1.
> [27-May-2022 15:10:12 UTC] The
> Automattic\WooCommerce\Admin\API\Options::get_options function is
> deprecated since version 3.1.

According to the Github pull request that was raised the fix will be released with WooCommerce core 6.6.0.

https://github.com/woocommerce/woocommerce/issues/32863#issuecomment-1128327458

Thanks!

Hi there, after my host cleared the cache, the problem still persists. When I try to create a new product, and select “Variable product”, it doesn’t want to update and publish the product.

Hi @nicolenoppe

You mentioned that it states (Read more) instead of (Select options). This makes me wonder if the product you are referring to is actually a product or a post? You’d want to double check and confirm that it is not a page or post.

after my host cleared the cache, the problem still persists. When I try to create a new product, and select “Variable product”, it doesn’t want to update and publish the product.

Since it has given this error get_options function is deprecated since version 3.1 the problem you are encountering can be attributed to the github issue indicated above. A fix is to be released with WooCommerce core 6.6.0, so a wait would be worthwhile.

Thanks

Hi!

Yes, I’m sure it’s a product. It has been purchased in past orders and is showing under “products”. This problem only recently started happening.

I’ll check into the github issue and see if the problem resolves with the update, thank you.

Hi @nicolenoppe

I’ll check into the github issue and see if the problem resolves with the update

Sounds like a plan! ??

I will go ahead and mark this thread as resolved, but please let us know if any additional issues arise after the update.

Thank you!