Closed
Bug 535675
Opened 16 years ago
Closed 16 years ago
Typing +foo in the QuickSearch box throws an "uninitialized value" warning (missing 'order' parameter)
Categories
(Bugzilla :: Query/Bug List, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 3.4
People
(Reporter: LpSolit, Assigned: LpSolit)
References
Details
(Keywords: regression)
Attachments
(1 file)
|
686 bytes,
patch
|
wicked
:
review+
|
Details | Diff | Splinter Review |
Use of uninitialized value in pattern match (m//) at /var/www/html/bugzilla-pg/buglist.cgi line 858.
$vars->{'message'} = 'buglist_sorted_by_relevance' if ($cgi->param('order') =~ /^relevance/);
'order' is undefined when called from QS. I cannot reproduce when using 3.4.4, so it seems something regressed this in 3.5. Marking as blocker as it's filling my error log.
Flags: blocking3.6+
Comment 1•16 years ago
|
||
Looks like I noted this problem in bug 503806. Fixing that bug should fix this problem (use relevance sorting for QS).
| Assignee | ||
Comment 2•16 years ago
|
||
I disagree to sort by relevance when using QS, for the reason given there. So the right fix for now for this bug is to check if the 'order' parameter exists.
Assignee: query-and-buglist → LpSolit
Status: NEW → ASSIGNED
Attachment #419789 -
Flags: review?(wicked)
Updated•16 years ago
|
Attachment #419789 -
Flags: review?(wicked) → review+
Comment 3•16 years ago
|
||
This is also needed on 3.4 branch because I can reproduce same error by doing a content matches Advanced Search without specifying specific order.
Flags: approval?
Flags: approval3.4?
Target Milestone: Bugzilla 3.6 → Bugzilla 3.4
Version: 3.5.2 → 3.4
| Assignee | ||
Updated•16 years ago
|
Flags: approval?
Flags: approval3.4?
Flags: approval3.4+
Flags: approval+
| Assignee | ||
Comment 4•16 years ago
|
||
tip:
Checking in buglist.cgi;
/cvsroot/mozilla/webtools/bugzilla/buglist.cgi,v <-- buglist.cgi
new revision: 1.409; previous revision: 1.408
done
3.4.4:
Checking in buglist.cgi;
/cvsroot/mozilla/webtools/bugzilla/buglist.cgi,v <-- buglist.cgi
new revision: 1.394.2.7; previous revision: 1.394.2.6
done
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•