Removing individual filters removes all filters


  1. Dave H.
    March 23, 2019 @ 12:31 pm

    I’m struggling to reproduce this in my dev environment. I can see it on your site, but I cannot reproduce it.

    Can you tell me what settings you have for your widgets?


  2. Erik d.
    March 23, 2019 @ 1:27 pm

    These are my settings:


  3. Dave H.
    March 28, 2019 @ 10:52 am

    Ok – so this is happening inside a *single taxonomy*. e.g. if users search for Blue, Black and Red dog toys (with either expand or narrowing set for multi-select) then when the user removes Blue it removes ALL the colours.

    From what I see, it’s definitely not removing OTHER taxonomies. e.g. if you have blue, black (colour) + leather (material), then you click to remove leather, it is retaining blue and black, and similarly, if you remove blue the bug remains that it removes blue and black, but it’s not removing leather.

    Can you please confirm this is an accurate description?

    I’ll get this fixed in next update.


  4. Erik d.
    March 28, 2019 @ 6:54 pm

    Yes that is correct. Thank you.


  5. Dave H.
    April 30, 2019 @ 3:24 pm

    There’s an additional bug here, possibly only in dev version, if a filter is removed and the remaining URL is just the category, then it should revert back to the /product-category/ permalink to avoid duplicate URLs.


  6. Dave H.
    April 30, 2019 @ 4:49 pm

    This bug has been fixed in the dev version.

    Additionally, the following bugs were fixed:

    Removing final attribute filter, if category is present, will revert back to the category URL. If final attribute removed but no category, the remove attribute link will revert back to the shop URL.

    Also – if permalinks were enabled, but not all permalinks were set up in the ‘permalink ordering’ section, this was causing those filters to be missed. This was clearly an edge case as you’d normally set the ordering for all your items in the permalinks and only exclude certain items from the canonical URLs.


  7. Erik d.
    May 5, 2019 @ 10:34 am

    Was this fix implemented in version 2.14 already?


Leave a Reply

Your email address will not be published. Required fields are marked *

We use cookies

We use cookies for various things on our site, including our on-site chat bubble (if you use it), our comment forms (if you use them) and for session handling (if you log in).

Other than that, we use cookies to identify where traffic came from to help us understand which traffic turns into sales, we use a cookie for Google Analytics traffic analysis and we use a cookie to customise adverts for our own products we think you'll be interested in.

You can read more detail in our privacy policy page. Please click 'Accept' or 'Decline' to continue.