Closed Bug 979383 Opened 11 years ago Closed 11 years ago

Simple Search for words triggers "The custom sort order specified contains one or more invalid column names: relevance desc"

Categories

(Bugzilla :: Query/Bug List, defect)

4.4.2
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 472496

People

(Reporter: merhan.oeztuerk, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36 Steps to reproduce: I have installed the latest stable bugzilla version on a clean, new debian vm. The backend is a mysql Database 5.5.8 on another host. Everything except the simple search works fine. Also the advanced search and the quick seach return correct result sets. Actual results: When I enter Search tokens in the field "words" the resutset is empty. When I only the fields status and product the resultset is correct. The following message occurs on the result page. "The custom sort order specified contains one or more invalid column names: relevance desc. They have been removed from the sort list." The advanced and quick search work fine and on the result page of these searches the message does not occur.
(In reply to Merhan from comment #0) > When I enter Search tokens in the field "words" the resutset is empty. > When I only the fields status and product the resultset is correct. This is missing a word.
Summary: Simple Search does not work when searching for words → Simple Search for words triggers "The custom sort order specified contains one or more invalid column names: relevance desc"
Sorry: > When I only USE the fields status and/or product the resultset is correct.
The message you get is not a real error. You can simply ignore it. That's bug 768892. Getting no results is caused by bug 472496. You probably only have a bug or two in your DB, making the fulltext index unusable. But having only a bug or two in a DB is an edge-case.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.