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
Is your enhancement related to a problem? Please describe.
Although WooCommerce made the woocommerce_hpos_pre_query filter available, the implementation of #3476 is not a small lift: as queries are built directly as SQL strings, we would need to translate them back to an Elasticsearch query.
In the meantime, we can conditionally declare the plugin incompatible with WooCommerce HPOS, using the snippet provided here.
We will need to account that:
We only run Elasticsearch queries for orders if both the WooCommerce AND the Protected Content features are enabled.
WooCommerce Orders Autosuggest works fine with HPOS (but only in compatibility mode)
Designs
No response
Describe alternatives you've considered
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is your enhancement related to a problem? Please describe.
Although WooCommerce made the
woocommerce_hpos_pre_query
filter available, the implementation of #3476 is not a small lift: as queries are built directly as SQL strings, we would need to translate them back to an Elasticsearch query.In the meantime, we can conditionally declare the plugin incompatible with WooCommerce HPOS, using the snippet provided here.
We will need to account that:
Designs
No response
Describe alternatives you've considered
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: