This page is a product archive page, that shows all products related a specific attribute, called “composer”. This is uses the standard woocommerce url for a specific attribute for a composer.
I have the new “filter - search” component on this page. When you search for something, it correctly filters the product list. However, when you clear the search field, it incorrectly resets the query to show the entire product list, not the product list scoped to the “michael-moerane”.
If there is another filter on the page set to the product attribute “composers” and “Moerane” is selected there , removing the search term correctly resets the product list to only Moerane’s products.
It seems the filter isn’t honouring the query that happened at page load.
Do you have an issue with all filters? Because for me the only filter that still had an issue was the radio button filter combined with other filters and that is supposed to have been fixed in 1.9.9
I wonder if anybody from the Bricks team read my issue carefully the first time or if I was unclear, although it was dismissed as being the same with this issue pretty fast.
I even provided this link to the website having the issue in my original report but did anyone check it?
I have a category archive on a news website that has three select filters on it for filtering by author, tag, or subcategory. Whenever I apply a filter via AJAX and then remove or change the filter the archive page stops working altogether and starts displaying posts from every single category on the website.
When I wrote about this issue I did so because I was starting to have the same issue with a pagination element on yet another website, so I realised it is not a server configuration problem or a localised one. So I wonder how are filters production ready in the following release if using them on archive pages breaks the archive?
Maybe I am doing something wrong, but I would really like some assistance since my archive works just fine before applying said filter, but stops working after setting any filter, so it’s not a problem with the configuration of the archive either.
Sorry for the tone of my last reply. It was rather frustrating to find that my issue was dismissed so fast and it persists through updates that claim to solve it.
I’ll create a temp admin and share the credentials. Could you tell me what email address would be the one I should send them to?
It’s help@bricksbuilder.io@blureogroup.
Please make sure to add a link to this and the other thread, using the email address you used during the purchase.
Thanks for working on it! I signalled it again since I think filters are mainly used on archives. So I consider it very important that in order to launch them out of beta they should work on archives.
Let me know if you still need admin credentials or if I can disable the account.