Incorrect order of search-result
|Status:||Under Review||Start date:||2012-07-09|
|Priority:||Must have||Due date:|
The function execFinalQuery in pi/class.tx_indexedsearch.php, doesn't use the searched word(s) in exec_SELECTquery where filter anymore, so freq gets wrong.
|duplicated by Core - Bug #44600: Results doesn't honour the flagBitMask and so the order i...||New||2013-01-17|
Updated by Ralf Hettinger 23 days ago
Unfortunately, I can confirm this. Due to this bug indexed_search is rather useless imo: Ordering of results has nothing to do with the searched word(s) anymore :(
The following order settings are affected: rank_flag, rank_freq, rank_first, rank_count
An obvious consequence next to the wrong ordering of results: ###RATING### is being filled with nonsense. It is always 100% for rank_flag and rank_freq. And contains a quite large number for rank_count. For rank_first it's wrong, too, but that's not so obvious here. Thus, #44600 might be a duplicate of this one.