[Note: I added search links for ease of use, but am unsure whether they'll work as intended.]
Nice! I'd given up using the forum search for anything other than full release names, as simply typing in names or titles invariably came up blank, in my less than extensive experience. Case in point, searching simply for "
kylie" doesn't just fail to find that thread, it fails to find anything - or used to, anyway, now it finds your post, and soon it'll find my post too, heh.
Picking up where you left off, though, the problem seems to specifically be that underscores aren't recognized as whitespaces: "
kylie_minogue" does find the thread in question, along with a couple of others. Ditto, "
tension" fails, but "
tension_" works.
Which is nice to know, but doesn't quite answer the question why the full release name fails in this case. Poking around some more, my guess is that it's about the brackets, or rather the underscore-bracket sequence specifically. On the results page of your "
(Deluxe)-WEB-2023-ENRiCH" suggestion, it looks to me like the brackets aren't bolded, unlike the rest of the search string, and the HTML confirms that:
HTML:
Kylie_Minogue-Tension_(<em class="textHighlight">Deluxe</em>)<em class="textHighlight">-WEB-2023-ENRiCH</em>
Guessing again, that may have to do with brackets being subject to URL-encoding, as in "scnlog.me/forum/search/1?q=
%28deluxe
%29". At any rate, something like "
A_Storm_In_Heaven-(2016_Remastered-Deluxe)-BONUS_TRACKS", with no underscores next to the brackets, appears to be unproblematic.
Getting back to our thread, simply removing the brackets, "
Kylie_Minogue-Tension_Deluxe-WEB-2023-ENRiCH", doesn't cut it, but replacing them with dashes, "
Kylie_Minogue-Tension_-Deluxe--WEB-2023-ENRiCH", which are being recognized as whitespaces and are not subject to encoding, does. Yay?