Closed
Bug 65399
Opened 24 years ago
Closed 23 years ago
Query page falls over if product has no components.
Categories
(Bugzilla :: Bugzilla-General, defect)
Bugzilla
Bugzilla-General
Tracking
()
RESOLVED
FIXED
Bugzilla 2.14
People
(Reporter: CodeMachine, Assigned: tara)
References
()
Details
Attachments
(2 files)
2.72 KB,
patch
|
Details | Diff | Splinter Review | |
584 bytes,
patch
|
Details | Diff | Splinter Review |
Naughty, naughty, someone wasn't looking for other instances of a bug when they fixed it (bug #40987). But then, I can't talk, as I verified the bug. query.cgi should at least give a coherent error. It should probably also continue to work, but skip that product so the whole thing doesn't fall over because of one product (do we have the ability to allow different groups access to add components to different products?) If it does work probably, we should probably emit a warning in mail, query.cgi, the error log or something. Should check all the .cgis in the product. I'll try and get around to that shortly.
Comment 1•24 years ago
|
||
Comment 2•24 years ago
|
||
the patch I submitted also fixes a syntax error in the js in the latest CVS version of query.cgi. Basically, somebody put an "if(... in ...)" in, which AFAIK is not supported by most browser - it certainly breaks my NS4.76 (silently - the product/version/etc narrowing simply won't work) and my IE5.0 (with a bang).
Reporter | ||
Updated•23 years ago
|
Target Milestone: --- → Bugzilla 2.16
Reporter | ||
Comment 4•23 years ago
|
||
I know this wasn't considered a 2.12 blocker, but seriously folks, this problem comes up so often it is really getting annoying, and I'm sick of explaining it to people. I vote for this as a 2.14 bug by nominating it as a "release blocker". If I had have known how serious it was I would have nominated it as a 2.12 blocker. We'll save the time spent fixing it back quickly. We don't need to necessarily make the query page work, but we need to at least make it say what the problem is.
Severity: minor → major
Comment 5•23 years ago
|
||
agreed. But I'm not going to r= this patch. I could swear those 'var' statements in the javascript were removed for a reason in another bug. I forget the bug number though. If this patch gets split into the component fixes for the specific bugs, I'll r= the fix for the component problem.
Keywords: patch
Target Milestone: Bugzilla 2.16 → Bugzilla 2.14
Comment 7•23 years ago
|
||
Updated•23 years ago
|
Updated•23 years ago
|
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 8•23 years ago
|
||
The component bug fix has been checked in. The other chunk of the patch is not what was originally reported here, and it probably worth another bug if it's valid.
Reporter | ||
Comment 10•23 years ago
|
||
*** Bug 71296 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 11•23 years ago
|
||
*** Bug 85438 has been marked as a duplicate of this bug. ***
Users upgrading to 2.12 and finding themselves unable to log in, may comment out use strict; in query.cgi. Then go look through your products and make sure each has at least one component. Then go back and uncomment it.
Comment 13•23 years ago
|
||
*** Bug 90620 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 14•23 years ago
|
||
*** Bug 97109 has been marked as a duplicate of this bug. ***
Comment 15•23 years ago
|
||
Moving to Bugzilla product
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: other → unspecified
Reporter | ||
Comment 16•23 years ago
|
||
*** Bug 98030 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 17•23 years ago
|
||
*** Bug 105466 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 18•23 years ago
|
||
*** Bug 106563 has been marked as a duplicate of this bug. ***
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•