Skip to content
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

Instead of interpreting $args['tax_query'] use WP_Query->tax_query #2419

Merged
merged 8 commits into from
Mar 1, 2022

Conversation

felipeelia
Copy link
Member

@felipeelia felipeelia commented Oct 19, 2021

Description of the Change

While WordPress is parsing the WP_Query, it will get all taxonomy-related parameters like taxonomy, cat, category__in, etc., to build a big tax_query (see WP_Query::parse_tax_query()). This PR removes ElasticPress interpretation of those parameters to rely ultimately on that tax_query, as WP would do.

This PR is:
1. Still a proof of concept and should not be considered ready to merge
2. Should only be merged after we have all tests related to terms assuring we are really using ES.

Alternate Designs

If we don't do it this way, we will have to (re)write all the tax parameters in the ES way, which doesn't seem to be needed.

Applicable Issues

Closes #2407

Changelog Entry

Changed: Taxonomy parameters now reflect the WordPress parsed tax_query

@felipeelia felipeelia changed the base branch from develop to 4.x.x November 12, 2021 15:37
@jeffpaul jeffpaul linked an issue Dec 16, 2021 that may be closed by this pull request
@felipeelia felipeelia merged commit 5af6932 into 4.x.x Mar 1, 2022
@felipeelia felipeelia deleted the feature/wp-query-tax-query-param branch March 1, 2022 14:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

category__in search support for the post searches
3 participants