Bug #38767

Incorrect order of search-result

Added by Mats Svensson 11 months ago. Updated 22 days ago.

Status:Under Review Start date:2012-07-09
Priority:Must have Due date:
Assignee:- % Done:

0%
Category:indexed search
Target version:-
TYPO3 Version: Complexity:
PHP Version:
Votes: 1 (View)

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.

Related issues

duplicated by Core - Bug #44600: Results doesn't honour the flagBitMask and so the order i... New 2013-01-17

History

#1
Updated by Oliver Hader about 1 month ago

  • Target version set to (temporary)

#2
Updated by Oliver Hader about 1 month ago

  • Project changed from Indexed Search to Core

#3
Updated by Oliver Hader about 1 month ago

  • Category set to indexed search

#4
Updated by Oliver Hader about 1 month ago

  • Target version deleted ((temporary))

#5
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.

#6
Updated by Gerrit Code Review 22 days ago

  • Status changed from New to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20294

Also available in: Atom PDF