Claudiu Lodromanean

Jetpack is not required to use WooCommerce. You only need to use it if you are also using the WooCommerce Services plugin (e.g. for automated taxes), and WooCommerce does not forcibly install Jetpack (it is optionally installed while going through the setup wizard).

You should be able to use the woocommerce_single_product_image_thumbnail_html filter. See: https://github.com/woocommerce/woocommerce/blob/master/templates/single-product/product-image.php#L48

My apologies. It does seem that the percentage discount coupon has not been a fixed cart discount since WC 3.0 (it should now be a per product discount). The logic will be updated in the next WC version to allow mixed sale/non-sale items with percentage discount coupons. Thanks.

Hi @walkinverse,

The new behavior is actually the correct behavior.

The fact that percent discount and fixed cart coupons were allowed with mixed sale/non-sale items in the cart was a bug in the previous version of WooCommerce. You can see that the description of the checkbox to restrict coupons when items are on sale says: “Per-cart coupons will only work if there are items in the cart that are not on sale.”, and this matches the current behavior.

Hope this clears things up.

Thanks.

Hi,
What you are trying to do with the Products block does not exist yet. Thanks for opening the issue; we will investigate it for a future version of the block.
Thanks.

Hi there.

The products block is not intended to replace the main Shop page, and so does not have those sorts of features. It’s for featuring products in your regular posts and pages, similar to the products shortcode (https://docs.woocommerce.com/document/woocommerce-shortcodes/#section-6).

For your main store catalog you should still use a Shop page. (https://docs.woocommerce.com/document/woocommerce-pages/)

Hope this clears things up. Thanks.

Hi there,

Thanks for the report. I believe this is the issue you are describing: https://github.com/woocommerce/woocommerce-gutenberg-products-block/issues/81

It seems to be caused by the way the Gutenberg editor handles the API requests used for the search autocomplete. We are currently investigating fixes for it, and it should be patched in the next release of this plugin. In the meantime, I believe typing more slowly into the search field should prevent the issue from happening.

Hi there,

Thanks for reporting this issue. I was able to reproduce it and have created a ticket for it at: https://github.com/woocommerce/woocommerce-gutenberg-products-block/issues/101

It will be fixed in a patch release coming soon.

Yes! We’ll have it as soon as possible, but we want to make sure we don’t break a bunch of sites. ??

That plugin is still in development and not ready for live sites, so I wouldn’t use it if you are not experienced.

Having things in custom tables is going to be a big speed boost compared to having everything stored in metadata.

The project is still active and being worked on, but it is a big change and the changes will be in WooCommerce core in a major release like 4.0 or 5.0.

WooCommerce doesn’t have post-to-FB features on it’s own. There is going to be some plugin you are using that handles those features.

Looks like that site is using Goodstore theme 2.0, but the latest version is 3.0. I’d try updating the theme and see if it fixes the issue.

Display options have been moved to the Customizer so you can have a live preview while setting them. There is a notice with this information at the top where the display settings used to be (unless it’s been dismissed), but you can access them through the Customizer > WooCommerce section.

If product pages are being shown as a blog post that means you probably don’t declare WooCommerce support in the theme. Declaring WooCommerce support in the theme should solve the issue. See this post and the linked guide for more information: https://www.ads-software.com/support/topic/guide-for-declaring-woocommerce-support-in-themes/

You need to declare WooCommerce support in the theme: https://github.com/woocommerce/woocommerce/wiki/Declaring-WooCommerce-support-in-themes

This should be fixed in 3.3.2: https://github.com/woocommerce/woocommerce/pull/18883 You can apply that patch yourself if you’re comfortable with that, otherwise we will be releasing 3.3.2 as soon as possible.