-
Notifications
You must be signed in to change notification settings - Fork 219
Spilled icecream (js error) with Filter Products by Attribute when store has no attributes #2441
Comments
@haszari I've moved this to the backlog for now. However, if you can't reproduce on a released version of the blocks (or WC core), then note that in the issue and I'll consider giving it a higher priority. |
It's an edgecase, but would still be nice to give some feedback to merchants when they are configuring the filter block in the backend to that they have fair warning they need to setup some attributes before using the block. With that said, since this has been out in the wild for a while now (thanks for verifying ✋) and there doesn't seem to be mention of it surfacing anywhere, I think we can leave it in the backlog and pick it up as a cooldown task at some point. |
This issue has been marked as |
This issue has been marked as Internal: After 10 days with no activity this issue will be automatically be closed. |
This issue has been marked as Internal: After 10 days with no activity this issue will be automatically be closed. |
This issue has been marked as Internal: After 10 days with no activity this issue will be automatically be closed. |
This issue has been marked as Internal: After 10 days with no activity this issue will be automatically be closed. |
To reproduce
Filter Products by Attribute
block to a page or post, publish.TypeError: Cannot read property 'id' of undefined
We probably need some checks to render nothing / placeholder if the store has no attributes.
The text was updated successfully, but these errors were encountered: