Closed Bug 233049 Opened 21 years ago Closed 20 years ago

Software Error when filtering requests with component not in the selected product

Categories

(Bugzilla :: Attachments & Requests, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Bugzilla 2.18

People

(Reporter: rajesh.venkatesan, Assigned: Wurblzap)

References

()

Details

Attachments

(3 files, 2 obsolete files)

User-Agent: Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 Firebird/0.7 When placing a request as a new user, " There is no component named Template::Document=HASH(0x864c6d8) " comes up. Reproducible: Always Steps to Reproduce: 1. Create a new user account. 2. Click on Requests. 3. Set the Product to Bugzilla and component to Account Manager. 4. Click on Filter. Actual Results: I've attached a zip file containing the page with the error message.
Attached file Page containing error (deleted) —
Confirming. We have two problems here.... 1) The error message isn't picking up the selected component correctly 2) This should be a ThrowUserError (so they get a polite message saying the product and component were mismatched) not a ThrowCodeError (which indicates something was broken, which it isn't). Optionally, we should play like the query page and use javascript (if the user has javascript active) to repopulate the component list so only the valid components are there when a product is chosen.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: crash if a request is placed to the account manager component and filter is clicked → Software Error when filtering requests with component not in the selected product
Flags: blocking2.20+
Flags: blocking2.18+
OS: Windows 2000 → All
Hardware: PC → All
Target Milestone: --- → Bugzilla 2.18
Blocks: 244831
Attached patch Obvious patch [trunk] (obsolete) (deleted) — Splinter Review
I'm mystified why ThrowUserError picks the component name up while ThrowCodeError doesn't.
Assignee: myk → wurblzap
Status: NEW → ASSIGNED
Attachment #166117 - Flags: review?
Attached patch Obvious patch [branch] (obsolete) (deleted) — Splinter Review
Attachment #166118 - Flags: review?
Attached patch Obvious patch, take 2 [trunk] (deleted) — Splinter Review
Attachment #166117 - Attachment is obsolete: true
Attached patch Obvious patch, take 2 [branch] (deleted) — Splinter Review
Attachment #166118 - Attachment is obsolete: true
Attachment #166117 - Flags: review?
Attachment #166119 - Flags: review?
Attachment #166118 - Flags: review?
Attachment #166120 - Flags: review?
Whiteboard: patch awaiting review
Attachment #166119 - Flags: review? → review+
Attachment #166120 - Flags: review? → review+
Flags: approval?
Flags: approval2.18?
Whiteboard: patch awaiting review → patch awaiting approval
Flags: approval?
Flags: approval2.18?
Flags: approval2.18+
Flags: approval+
Whiteboard: patch awaiting approval → patch awaiting checkin
Checking in request.cgi; /cvsroot/mozilla/webtools/bugzilla/request.cgi,v <-- request.cgi new revision: 1.14.2.1; previous revision: 1.14 done Checking in template/en/default/global/code-error.html.tmpl; /cvsroot/mozilla/webtools/bugzilla/template/en/default/global/code-error.html.tmpl,v <-- code-error.html.tmpl new revision: 1.39.2.1; previous revision: 1.39 done Checking in request.cgi; /cvsroot/mozilla/webtools/bugzilla/request.cgi,v <-- request.cgi new revision: 1.17; previous revision: 1.16 done Checking in template/en/default/global/code-error.html.tmpl; /cvsroot/mozilla/webtools/bugzilla/template/en/default/global/code-error.html.tmpl,v <-- code-error.html.tmpl new revision: 1.41; previous revision: 1.40 done
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Whiteboard: patch awaiting checkin
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: