Compatibility with Divi Filter Grid

Hi!

The new instance of the $wp_query explains the issue, as it’s not longer the main query, and the override method does not trigger.

Before jumping into coding, you should try this option first. This will bypass some query checks and more likely triggers the override, often time this is all it takes.

As for the integration, there an attribute to set on the $wp_query object – but it happens to have a bug with the current release (what a coincidence), still it’s possible to make it work.

Integration for plugin devs to trigger the override

Normally, if the following query variable is set, the plugin will trigger an override, this is all they need to set in the filter grid plugin in $wp_query to integrate:
$wp_query->set( 'asp_override', true );
When this query variable is set, the plugin will trigger the override. Please let them know 🙂

I’m also attaching a patched beta release to this reply, that has the query variable fix included.

Thank you very much!

Do you mind if I ask if this the folks had to change something in the divi grid, or you only had to add an option somewhere? I’m curious as then I can add a demo to the website with the Divi filter grid too 🙂

It is because of the var_dump, because it pollutes the json response, that the divi filter grid tries to parse – that of course will break, that’s expected when you change the output, but it’s not related to the search.

I’m afraid there it’t not yet documented, but it’s a simple boolean value of true or false. When true, it will signal Ajax Search Pro to capture and cancel the current query and replace the results from it’s own query results. That’s all it does 🙂

/**
 * When true, Ajax Search Pro will capture the $wp_query (WP_Query) in the following way:
 * -> on "posts_request" hook it checks if $wp_query->query_args['asp_override'] === true
 * -> if true, cancels the current query by setting the request $request = ''
 * -> on "posts_results" hook checks again, and overrides the posts returned with the results from it's own query
 * This means that the original query is cancelled, then the results are swapped.
 **/
$query_args['asp_override'] = true;

That could be very likely resolved from our side.

Can you ask if they use any special ordering arguments or are they setting it in the query args like in WP_Query? If so, can they let me know which ones exactly?
Also, is there a query argument similar to the “asp_override” or anything special that their plugin sets, so I can reliably detect if the query is related to the filter grid?

With that I can very likely add a minor modification to the plugin code to explicitly set the same ordering arguments.

Great!

I’m attaching a modified version, which checks this variable and changes the ordering accoding to the query ordering. I was not able to test it ufnortunately, so I’m only guessing. If you see no change, then can you please add temporary back-end and FTP access? I will try to directly debug through the code, this should be solvable in my opinion.

Thank you!

I may have found a possible solution. Please note that the search filters can’t be used, as those are not sent along with the ajax request when the sorting is triggered within the filter grid. (that is actually how it should be, so it’s perfectly fine)

Can you please disable all front-end filters, especially the generic filters on the search bar. With the filters the parser would assume that the checkboxes were unchecked and those fields would be disabled. There is unfortuantely no way to technically send that filter data along, as you can have multiple search bars and it would be super hard to tell which data is relevant – overall it would be a mess.

Either way, after disabling the filters it should apply to the filter grid as well, and give you very close results as if the actual live search was used.

Hi Ernest! It sorta worked, but when I sort the results by date or author it only shows one post and the others disappear.
That is because of the filters as I mentioned previously.

It’s going to be either or, no way to combine them both – if you turn off the sorting and all other filters on the divi filter grid and use the filters from ajax search pro, that should still work in combination with the Results Page live loader feature. In you case use the #fs-search query selector: https://i.imgur.com/4xxO8IT.png

That will reload the results page in the background with the new parameters that will apply on the filter grid. Anything that is loaded via ajax within the filter grid should be also turned off – especially pagination. If there is only an ajax “live” pagination possible, then it might be a good idea to show more results and turn off the pagination.

With that however you could probably use a different module. Divi probably has like an archive page module specifically for search results, those should work right off the box as those are designed for archive pages (including the search results).