Search by Relevancy new error

[Rydenlol]

Hi.

So after I upgraded to 4.2.7, the search by relevancy option no longer triggered an error. However, what it does now within the results, is it adds "/&searchlight=1" at the end of the page url of the result which then forces a "Page Not Found Error code: 2T251/5" 

Easily enough, removing that last bit will send me to the page but I can't expect end users to know that. I have narrowed down the issue though. Since IPB does not have an option to search by relevancy by default, I use Kitchen Sink to force it. Kitchen Sink also forces the searchlight text as mentioned above. When I disable Kitchen Sink, search for something, and manually select more relevant results, the issue does not occur. But, I cant have my end users either missing searches or having to select "more relevant results" every time they search. At least that's not ideal lol.

In short, I assume this is on Kitchen Sinks end but wanted to see if anyone knew of any workarounds to achieve default search by relevancy.

Edited January 15, 2018 by Rydenlol

[titcrunch]

for the moment searchlight can't work you need wait ips 4.3 with elastic search for this

Edited January 15, 2018 by titcrunch

[Rydenlol]

Okay, so I'll need to disable that part of Kitchen Sink then. Has there been any functionality added to 4.2.7 to default search by relevancy or is this all going to have to wait until 4.3?

[titcrunch]

no 0 add in 4.2.7 only fix bug all the major add come in 4.3

[Rydenlol]

Fair enough, marked as answered. Thanks again sir.

[Cookie Monster]

The question(s) in this support topic have been answered and the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.