Bug Report: Facet-filters show incorrect count when used together - FIXED

When using multiple facet-filters in nopAccelerate, the total-counts show the wrong numbers.
I seems like the facet-filters for Price, Manufacturer and Specification Attributes work independently from each other.

Example on demo.nopaccelerate.com:

- Go to http://demo.nopaccelerate.com/notebooks
- Change the price-filter to select notebooks between $10 and (around) $1500
- The Manufacturer-filter shows a count of (2) HP laptops, but when you select the "HP" filter, only 1 laptop will be shown. This is a bug.
- The "Memory" filter now shows a count of (1) for the "3 GB" option; however when you select this option, it shows a count of (2). But still one result is shown? What's happening here?

This behavior is kind of alarming and makes me feel like nopAccelerate is not a stable product yet.
Hope you can fix this.

thanks,
Dion

Hi Dion,

Thank you for reporting. It is a bug, it seems that pricing filter is applied but the facet count is not refreshed when pricing is applied. I have created an issue for the same. This is an important feature and will be fixed soon.

When you select the filter, it updates count. It is designed this way. It display a count of other facets as if this filter had not yet been applied. Its not a bug, but a preference on how you would like it to behave. However, currently there is no way to disable it.

What would you suggest here? An option using which this can be disabled should be good?

Please note that nopAccelerate is relatively new product, and like any other software it may have unexplored bugs.

Moreover, we're working on fixing all the known issues and bugs on immediate basis. And we appreciate your help in finding and offering ways to fix it. :)

Thanks,
Krunal

Hi Krunal, thanks for your fast response. I understand nopAccelerate is a relatively new product, and you've really done a great job integration nopCommerce with Solr.
However, as I think facet-filtering is one of the "killer features" of your product, this should work flawlessly. And at this moment, the multi-select facetting doesn't work like expected.

Example:

- Visit http://demo.nopaccelerate.com/notebooks
- Select "HP" from the "Manufacturers" -> this will hide the "1 GB" option from "Memory" (which is as expected) and still shows the the "ASUS (100)" as multi-select in the "Manufacturers" (also as expected).
- However, when I now select the "3 GB" option from "Memory", a new option "1 GB" show up (which is _not_ expected).
- Now when I select "ASUS" from the "Manufactures", I get 0 results (now I'm completely lost :-)

Can you see what I mean? Each filter should be aware of selections made in other filters, and at the moment it's not behaving like expected.

regards,
Dion

Hi Dion,

We appreciate you understanding it and helping us improve this.

This is actually caused by the same bug which is related to bug in manufacturer filter.

Moreover, I certainly agree with you that it should work flawlessly and each filter should be aware of selections made in other filters.

Please note that we're already working on it and update it shortly along with few other bugs.

Thank you,
Krunal

Hi Dion,

Please find the updates on the issues you have reported.

Note that, none of them are yet published on demo site. We're working on these and will update everything very shortly.

Dion wrote:

This issue is fixed. As you guessed, the issue was in the manufacturer filter query.

Dion wrote:

This is caused for two different bugs.

The first one is about the condition which is applied with multi-faceting, due to which you get 0 results instead of the few products that should be available. This is also fixed.

The another is - when you select 3 GB from memory.. it shows a new option 1 GB.. which is not expected. This is actually related to the tagging for multi-faceting that is used to describe the constrains in which facets is applied. We got the issue, and at the moment working on a solution to do this tagging properly that will resolve this issue.

We will update here as soon as a we complete this and update it on our demo store and release this new build.

Once again, thank you for helping us with this!

Krunal

Hi,

This bug is fixed and we also updated the demo store. Please check the same.

Once again, we appreciate your help! :)

Thanks