You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Magento Version : Magento CE 2.2.5
ElasticSuite Version : 2.6.1
Environment : Developer
Third party modules : Not related to layered navigation and products lists.
Good afternoon,
This is a report about the issue #1042.
The pull request #1051 doesn't seems to solve the problem.
There are still many filters which have only one option :
Have you tried yourself your new release to know wether it fix this issue or not ?
Ilan
The text was updated successfully, but these errors were encountered:
Please, don't be so salty when submitting an issue ...
PR #1051 will hide a filter if it has only one value that matches the entire product collection.
As I can see on your screen, the "Avec rallonge : Oui" is matching 5 products among 6 results.
In this case, the filter is relevant and should not be hidden, because if you apply it, it will remove one article from the list.
So imho, your case is invalid. We'll be glad to dig more if you are able to reproduce it on a proper use case (would be correct if "Avec rallonge : Oui" was matching 6 products here).
You misundertand me, I was not sure if it was the correct behavior of your extension.
As I know, the field yes/no did not show up the filter No option.
Which is defined for the last product of this example list.
I have this situation with complementary module of ElasticSuite, Ratings.
Is this related to the core or to the complementary module ? Or is it the expected behaviour ?
Preconditions
Magento Version : Magento CE 2.2.5
ElasticSuite Version : 2.6.1
Environment : Developer
Third party modules : Not related to layered navigation and products lists.
Good afternoon,
This is a report about the issue #1042.
The pull request #1051 doesn't seems to solve the problem.
There are still many filters which have only one option :

Have you tried yourself your new release to know wether it fix this issue or not ?
Ilan
The text was updated successfully, but these errors were encountered: