I noticed recently that using a Category in the Filter element works well but only when on the main Products page however it does not work when run from a child category. When running from a Child category page, it shows no products because it’s doing a search from within the Child category instead of the Parent Products page. I’d assume that using the Filter Categories would allow a user to jump to any category they want, however that does’t appear to be the case.
Unsure if this is a defect in the design or if it’s working as expected and there’s a different way to achieve the use-case to allow users to go to different categories quickly.
Part of me is assuming this may be as designed as then Filter is filtering from the page it’s being run rather than from the main Products page, however in that case why would it show categories which aren’t relevant or underneath the Child category page? Either way it seems there may be a defect here or at least a poor design, but also totally open to this being something easier that I’m just missing perhaps. Happy to be shown how to do this or to have this treated as a defect either way.
Hi @itchycode , I see that you changed the title to “WAIT”… is there anything waiting on me currently or anything I can do? Or was this meant to be a “WIP” instead?
Thank you for clarifying. I’m a bit hesitant though on that… if the filters are meant to be filters from the existing category (as opposed to the product roots / all categories), why would it display all categories still? That behaviour seems strange to me. If it was a multi-select box then I’d maybe see the “Category C and Category A” filtering, but not really when it’s a single dropdown.
I’ll see if I can try the term query loop suggestion though, that may work. Thanks, Jenn.
So sorry if the product filter confusing you.
As for the filter input type, Bricks is supporting the checkbox as well if that’s making more sense
You could find it here.
The problem I see is that the “Category C and Category A” would make sense if it were a select, but in the situation where the Input is Dropdown for example, I’m not sure if that totally makes sense. If it’s a Dropdown, I think a user would expect to see the filters that actually have results be what displays or at least all sub-categories rather than root-level categories which aren’t even valid at all for subcategories.
Hopefully that makes a bit of sense, not sure if I’m explaining it very well.
Maybe this is where the documentation can be improved so it actually goes over how we expect the Taxonomies filter to work in the Products Filter element as it’s just not behaving how I’d expect it to currently.
Somehow thought i tested this and that it worked. I don’t know why i used it this way. It made sense as a dropdown for navigation to let visitors quickly switch to another category page. I do understand how it works, but with a long list of things for Woocommerce sites i can easily miss something in the end.
Now i need to figure out if i go make a dropdown menu (site going live soonisch) or wait with that for 1.8 release which can do this nav dropdown with a query in 3 mouse clicks.
I have the problem that the archive template ( overview products with filter ) that is also used as categorie page, the filter part is not working, how can i fix this? Iam only use bricks filters.
Hi @PEDROW ,
Since this report is over a year old: Can you please create a separate report and describe the issue in more detail by providing a live link and in the best case, a screen cast showing and explaining your setup? Thanks!
I’m having the same problem as you’ve reported here. And it seems to me that there’s something wrong with the product filter from bricks.
I’ve created a template for product archive, which is applied to both the “shop” page and on the various product categories pages.
On the shop page, the filter works fine, but in the product categories pages, the filter doesn’t work properly because, for example, it picks up all the attributes, tags and prices from all the products and not just from the products in that category.
Shouldn’t the filters only show data from the products in the current category? This way there is no sense to use it on product category pages!
I will open a new topic on this, as @timmse suggested.
Perhaps we can change this title from “NO BUG” to “WIP” then if it’s agreed that it’s something needing to be changed and is currently in progress?
No, because your report is about the products filter. The task I’m talking about relates to the search & filter features, which offer significantly more options in the long term than the “simple” products filter, which is sufficient for simple requirements.
Oh I see, I didn’t realize there was talk of two completely different filtering solutions here. Got it. So the original Woo Product Filter isn’t being changed or enhanced. It’s basically recommended that we use the newer Bricks Filters instead. Understood. Thanks for clarifying.
