Darren Ethier

Folks, I suspect these errors are happening while WooCommerce or the theme is being updated. There's a short window when updates are happening where visitors to a site might hit...

I agree with Albert's assessment.

Thanks for the suggestion. Right now it doesn't line up with the [current prioritization](https://github.com/woocommerce/storefront/blob/trunk/STOREFRONT_STATUS.md) we are giving to work so it's unlikely to be something implemented anytime soon.

Hmm, this is going to be an interesting one to work on. Some suggestions for whoever picks this up: - Would be good to see if this is isolated to...

I think what you've done so for @mikejolley helps narrow it down further. @zhongruige given Mike's findings, and this doesn't appear to be a blocks specific issue, does that give...

Given [MIke's assessment here](https://github.com/woocommerce/woocommerce-gutenberg-products-block/issues/3955#issuecomment-804126274) - since WooCommerce blocks is simply using a WooCommerce core API for getting what image to display. The error also suggests it has something to do...

Thanks Thomas for the investigation. Item 4 in your list appears to be an important part of the discovery process that should be handled by the product image uploader for...

Also @JoshuaGoode, at this point, this is looking less like an issue that is related to anything Woo Blocks is doing and more of either a WP core, WooCommerce Core...

@gigitux or @sunyatasattva, where is(are) the relevant PR(s) for the [GB fork](https://github.com/sunyatasattva/gutenberg/tree/add/build-query-vars-from-query-block-filter) mentioned in this pull request? I recall someone sharing the PR link with me at some point but...

> We didn't create any PR. Why not? Even if it's created as a draft, it can help with discussion around implementation for this use case. Code freeze for WP...