Marco1970

Ignore ??

much appreciated, TY

HA … a big RTFM to me!!!

works like a charm ??

TY

M

Hi Mikko,

thanks for reply. They are one of the standard Woo product types, alongside Simple, Variable, Group, etc. But all good, they are indexed as expected, my bad ??

If I may piggy back with another Q to make sure I understand correctly:

It seems to me that Relevanssi indexes all Products except those marked as hidden for ‘search’ (regardless of ‘catalog’ setting), correct? Or the search visibility setting only affect the display of the result (i.e. Relevanssi ignores it)?

TY

M

Hi,

sorry for late reply, and thank you so much for the reply, super helpful! one Q if I may:

is the re-sync always whole? or MC uses internal product IDs and order IDs to start from where it left last time?

TY

M

Brill! TY

Brilliant, thanks!!! setting set , will keep an eye on things

TY

M

Hi,

thanks! makes sense, let me try

m

Hi Mikko,

yes, that worked, thanks!!

M

Hi Mikko, thanks for quick reply, truly appreciate it.

sorry, my bad, I described poorly:

1) I serialize the WP Query vars, NOT the query itself nor the results:

global $wp_query;
$buffer_query = $wp_query->query_vars;
$buffer_query[‘fields’] = ‘ids’;
$buffer_query[‘nopaging’] = true;
$buffer_query[‘bapf_apply’] = true;
$buffer_query[‘bapf_save_query’] = true;
$ser = serialize($buffer_query);

Reason is that the results are paginated, max 25 per page, and when I need to rerun the query later I need the whole result set.

2) I unserialize as follows:

$buffer_query = unserialize($ser);
$query = new WP_Query($buffer_query);
$results = $query->posts;

3) Based on what you said in your kind reply, my guess is that when a WP Query is re-created from serialized vars, the Relevannsi ‘posts_pre_query hook’ is not called.

any way I can do that programmatically?

TY

M

>> “….I therefore wonder if I need to do the same for Relevanssi (or any processing of the WP Query before serializing it) in order to ensure the correct results”

…or any post-processing of the un-serialized query before running it…

whatever it takes ??

TY

M

and I can honestly say the combination of the two is the best and most powerful search / filter combo out there.

fantastic work both

but plz plz plz keep it 100% compatible across new releases… I almost fainted this morning…

M

Awesome, thanks!!!

so I understand: this fix was to allow the default woo filters to work with Relevannsi search results, right?

M

Man you are good!

spot on…

will you work on a permanent fix on your side, or do I add the snippet to all my sites?

absolutely love the combination of Relevanssi and BeRocket, so they need to coexist ??

TY

M

Hi,

I simply updated Relevanssi to the latest, and the BeRocket filters disappeared from the sidebar since they were all empty, with the JS console on Google Chrome giving me the error. Hence I assumed Relevanssi was the culprit ??

After I restored the previous version of Relevanssi, all went back to be fine.

I also tried the BeRocket Advanced setting ‘Fix Ajax issues’, which removed the JS console error, but still the filters were not visible, still empty.

I use the latest version of the BeRocket PRO plugin.

Not sure how you can reproduce it….

What DB errors did you get?

TY