Search broken

[Quin]

its working for me now, thanks

[gree]

@admin thanks it works just fine now

[possbottle]

@admin it's broken again... or at least very confused. it's showing me nonsensical results that have nothing to do with any specific booth item number if I shove that into the search box, unless I put what I'm looking for in direct quotations... and even that is spotty at best. If there was a daemon update done for the database search runs from, I think I can understand what happened here, different calls and all that... but it feels like I'm being given true garbage results and nothing is findable anymore.

Edit: I should probably mention that it's been like this for the past couple days, not just within the last 18 hours... when the site hasn't been down for blips during traffic congestion.

EDIT 2: I figured out what's happening - it's doing "Match any word" for both "match all words" and the former.

[admin]

doesnt really make sense to me, the search engine was only changed yesterday, before that no changes where made to the search functionality whatsoever

[admin]

looks fine to me?

[minene-uryu]

I ran into a similar issue as @possbottle
i also search for the booth-id to find the threads for it, and i only really noticed today (sorry, wasn't doing a lot with the current heat) that the search is also looking for common mistakes.

Example A: 8447945

This shows the thread for Nocturne Classmate, which is 8447954 instead of 8447945.

Other Examples:
8079767 finds 8079760 instead
8203998 finds Nightmare Hunt (correct) and then 8201998, and last 8239984

those were just the ones i saw today.

[admin]

searching for 8447945 finds 8447954, i can also confirm this, but this also means, that the one you originally looked for -> 8447954 is not available at all, unless im wrong here?

same for the others, 8079767 returns 8079760, because 8079767 is not available.

[minene-uryu]

Yeah, that's the right. Before it only showed "no results", which is the expected behavior.
Now it shows unrelated items

[possbottle]

as said, it's doing the same behavior as having "Match any word" set for both Match Any Word and Match All Words. That's the issue right now.

[admin]

this has been fixed.

[inu__]

bump

[inu__]

bump

[baibuhe]

bump