Problems with WooCommerce compatibility

Hey @lisaweb

Are you using AMP for WP on woocommerce?

If yes, I recommend you to use our AMP for WooCommerce plugin. you can get our AMP for WooCommerce plugin from here > https://www.ads-software.com/plugins/amp-woocommerce/

Hope it helps. Let me know if you have any questions. We are always here to help you.

Yes, we have that plugin installed & activated as well. So unfortunately that is not the problem. Any other ideas as to how to fix this issue? Thanks again for your help.

Hey @lisaweb

Thank you so much for using our plugin.

That’s really a strange issue. Could you please share the Website URL? where you see that phrase. So that I can help you to fix this issue.

I provided several, please click on the Google link above to see them.

Ours is the top result in the list.

Hey @lisaweb

I understand your issue.

Could you please confirm us one thing? Did you select any option, such as Product out of stock or product not for sale?

Why I am asking is because I would like to understand the issue in detail so that I can help you to fix that issue.

Thanks. The product is in stock. But I figured out from playing with the options that this notice appears when no price is entered into the product. And that’s because we are using our shop as a Catalog, and for some of them we don’t want pricing on the web.

To accomplish this, we are using the “YITH WooCommerce Catalog Mode” found here https://www.ads-software.com/plugins/yith-woocommerce-catalog-mode/”
and we have it set to:
“Hide and disable “Cart” page, “Checkout” page and all “Add to Cart” buttons”.

However, I am uncertain as to whether this plugin suppresses this notice, or if your plugin is reading it as out of stock when there is no pricing.

Perhaps there a quick way to suppress this notice on AMP pages as well?

Also, I just deactivated the “YITH WooCommerce Catalog Mode” plugin to see if it would make a difference – but it still doesn’t show that notice on the regular product pages – just the AMP pages. So pretty sure now, that it’s not being caused by that plugin.