'no components for this product' error does not PutHeader()

RESOLVED WORKSFORME

Status

()

P3
trivial
RESOLVED WORKSFORME
17 years ago
6 years ago

People

(Reporter: bugzilla, Assigned: myk)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

17 years ago
This error (in enter_bug.cgi) does not do a PutHeader(), which is not too
important, but it probably should, for consistancy.
(Reporter)

Comment 1

17 years ago
Created attachment 45228 [details] [diff] [review]
Patch to call PutHeader() in the case of a 'no components error'
(Reporter)

Comment 2

17 years ago
Can I just check: is it right/OK for me to add the patch and review keywords for
this, or should that be done by someone else, when they take a look at this?
(Reporter)

Comment 3

17 years ago
Also, when this error says to use the 'components' link to add components for a
product, should it also say something along the lines of:

'You may need your Bugzilla <A mailto Param(Maintainer)>Maintainer</A> to do this'

Comment 4

17 years ago
The patch and review keywords are the alert to those "others" there's a patch to
look at and you can put them on after (or even right before) attaching the patch
(provided you have the proper permissions :)
Keywords: patch, review
OS: SunOS → All
Priority: -- → P3
Hardware: Sun → All
Target Milestone: --- → Bugzilla 2.16
->New product Bugzilla
Assignee: justdave → myk
Component: Bugzilla → Creating/Changing Bugs
Product: Webtools → Bugzilla
Version: Bugzilla 2.12 → 2.12
This patch has been obsoleted by templatisation (not yet checked in, but being
reviewed.) We now use DisplayError() in that case.

Gerv
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME
clearing target milestone on resolved non-FIXED bugs so they'll get re-triaged
if they get reopened.
Target Milestone: Bugzilla 2.16 → ---
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.