Bug #38767
closed
Epic #65814: Make Indexed search extbase plugin shine
Incorrect order of search-result
Added by Mats Svensson almost 12 years ago.
Updated over 5 years ago.
Description
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.
- Target version set to 2222
- Project changed from 1382 to TYPO3 Core
- Category set to Indexed Search
- Target version deleted (
2222)
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.
- Status changed from New to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
These changes should also be applied to the Extbase based version of indexed search (experimental mode)
- Status changed from Resolved to New
- TYPO3 Version set to 7
- Is Regression set to No
Thanks for reporting, I'm reopening the issue
- Parent task set to #65814
- Status changed from New to Resolved
- TYPO3 Version changed from 7 to 6.2
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by Anonymous 
Updated by 
Updated by 
Updated by