In Catalogue->searchCatalogue(), searching via ElasticSearch starts after the class.catalogue.pre_search hook, and after the Customer Memberships are applied to the WHERE clause.
I do not find comparable $should array elements that would filter for these $where and $joins conditions.
The deliverable could, therefore, contain more or less records than otherwise, and pricing not the same as was searched (logged-in member prices displayed and used in the search, but then that would miss the mark on the prices being filtered for).
Any thoughts on making class attributes used in a getter method that delivers the $where and $joins arrays as they are, so that when ElasticsearchHandler->search() is executed, these optional query expressions can be implemented?
In
Catalogue->searchCatalogue(), searching via ElasticSearch starts after theclass.catalogue.pre_searchhook, and after the Customer Memberships are applied to the WHERE clause.I do not find comparable
$shouldarray elements that would filter for these$whereand$joinsconditions.The deliverable could, therefore, contain more or less records than otherwise, and pricing not the same as was searched (logged-in member prices displayed and used in the search, but then that would miss the mark on the prices being filtered for).
Any thoughts on making class attributes used in a getter method that delivers the
$whereand$joinsarrays as they are, so that whenElasticsearchHandler->search()is executed, these optional query expressions can be implemented?