Closed Bug 30348 Opened 25 years ago Closed 22 years ago

Request for a nicer message when product unknown in enter_bug.cgi.

Categories

(Bugzilla :: Creating/Changing Bugs, defect, P3)

defect

Tracking

()

RESOLVED FIXED
Bugzilla 2.16

People

(Reporter: CodeMachine, Assigned: bugzilla)

References

()

Details

(Whiteboard: [error] enter_bug)

Attachments

(2 files)

Hmm, there isn't an "extremely trivial" severity ...

I often type the above URL manually to save time, but sometimes mistype.  It
used to give a enter_bug screen with no data on it (eg no components), but now
it gives an error.

Either way it would be nice to get an error saying that you mistyped it.  Even
better if you get shown a list of close (fuzzy search?) matches.
tara@tequilarista.org is the new owner of Bugzilla and Bonsai.  (For details,
see my posting in netscape.public.mozilla.webtools,
news://news.mozilla.org/38F5D90D.F40E8C1A%40geocast.com .)
Assignee: terry → tara
the only way to figure out that you've mistyped a url is to try and fetch data 
from it. this strikes me as slow.
*** Bug 45206 has been marked as a duplicate of this bug. ***
QA Contact: matty
Whiteboard: Future-Target
moving to real milestones...
Target Milestone: --- → Future
Sorry Chris, I don't understand.  It's a lot faster to type in a URL than to
find a bookmark and navigate through two pages.
can you re-up the patch with diff -u instead of diff -c?  They're easier to 
review that way.
Assignee: tara → gavins
Keywords: patch, review
Target Milestone: Future → Bugzilla 2.16
Whiteboard: Future-Target
Component: Bugzilla → Creating/Changing Bugs
Product: Webtools → Bugzilla
Version: other → unspecified
Whiteboard: [error] enter_bug
Possibly a dupe of bug #100100, also with a patch.
Gavin: your current patch has you printing <h2> before Content-Type:, which is
not a good thing. Is this patch still relevant, and are you looking to get it
checked in?

Gerv
Gerv: 

I don't think this does print <h2> before the Content-Type:. If you still think
so, then I'll be happy to fix it, if you can show me where. 

This patch has been working fine here for a while (but then it's not as if it
ever gets tested much!)

And yes, I think either this, or the pretty similar patch on bug#100100 should
be checked in at some stage, as they both fix an unsightly 'Software Error' page.

(p.s. Thanks for all your work on the new link bar)
You'll need to look at this again when the templatisation gets checked in,
because that file has been spanked hard.

Gerv
We are currently trying to wrap up Bugzilla 2.16.  We are now close enough to
release time that anything that wasn't already ranked at P1 isn't going to make
the cut.  Thus this is being retargetted at 2.18.  If you strongly disagree with
this retargetting, please comment, however, be aware that we only have about 2
weeks left to review and test anything at this point, and we intend to devote
this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
This got fixed with templatisation. I now get:

Error
 
'foobar' is not a valid product.

Please press Back and try again.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Target Milestone: Bugzilla 2.18 → 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.

Attachment

General

Creator:
Created:
Updated:
Size: