-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: Incompatibility with WooCommerce Brands #2502
Comments
Related to #2129 |
Hi @slaxxarn , Would you mind providing if possible a copy of the plugin (if you can email that to the address in my profile that would be great) and a screenshare to check the difference with and without ElasticPress enabled? I'm using version |
Hi @oscarssanchez, We're using version 1.6.14 of the plugin. But widgets filtering by IN operator should not work if elasticpress is enabled, as you add a seperate tax query with AND or OR. As I stated previously, could you not just check if a query for the taxonomy already exist before adding another one? Will look into and test some other variations tomorrow, don't really have the time right not. Will get back in this issues after som testing. |
Closing per #2560 |
Describe the bug
When filtering on category pages with WooCommerce brands layered nav widget, nothing is shown because elasticpress adds a second tax query with field = slug and operator = and / or. While woocommerce brand adds/uses term_id as field and IN as operator.
The issue is in Facet.php and row 326 - 333. You add a tax query with field = slug and operator = AND / OR
Steps to Reproduce
Expected behavior
Don't add another tax query if a tax query for the same taxonomy already exists.
The text was updated successfully, but these errors were encountered: