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
Hello, I was trying to understand why my date_query was not working with ElasticPress. When disabling the EP plugin the query works, when activating it, the query does not work correctly.
After debugging and researching, I came up to this file: includes/classes/Indexable/Post/DateQuery.php
Which, as of today, contains this comment:
// @todo implement OR filter relationships.
Is there a plan to implement this soon?
Here is an example of my date_query, obtained in the debugging addon:
When using the OR relation and analyzing the resulting CURL request with the debugging tool, I can see that the "post_filter" parameter has nothing about years or date ranges, because that relationship has not been implemented yet.
I don't know EP plugin code much so I am not sure I could help with this. But maybe you have already planned to release this soon.
Thank you and kind regards
The text was updated successfully, but these errors were encountered:
Hello, I was trying to understand why my date_query was not working with ElasticPress. When disabling the EP plugin the query works, when activating it, the query does not work correctly.
After debugging and researching, I came up to this file:
includes/classes/Indexable/Post/DateQuery.php
Which, as of today, contains this comment:
Is there a plan to implement this soon?
Here is an example of my date_query, obtained in the debugging addon:
Another example:
When using the OR relation and analyzing the resulting CURL request with the debugging tool, I can see that the "post_filter" parameter has nothing about years or date ranges, because that relationship has not been implemented yet.
I don't know EP plugin code much so I am not sure I could help with this. But maybe you have already planned to release this soon.
Thank you and kind regards
The text was updated successfully, but these errors were encountered: