Closed
Bug 109240
Opened 23 years ago
Closed 23 years ago
second line of comment in email is too long when attachment created
Categories
(Bugzilla :: Attachments & Requests, defect, P2)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.16
People
(Reporter: myk, Assigned: myk)
References
Details
Attachments
(3 files)
1.72 KB,
text/plain
|
Details | |
664 bytes,
patch
|
myk
:
review+
myk
:
review+
|
Details | Diff | Splinter Review |
14 bytes,
patch
|
Details | Diff | Splinter Review |
When you create an attachment, a comment is submitted to the bug about it. Email then gets sent out about the attachment creation, and that email contains the comment. The second line of the comment is too long and looks really horrible.
Assignee | ||
Comment 1•23 years ago
|
||
The original bug which added the URL to the attachment was bug#66651. I think that was OK, in that the short description of the attachment started on the next line. Now, on line 487 of the new attachment.cgi, I think you need a new line after the '(id=$attachid)' bit, as this is where processmail turns the text into an URL
*** Bug 109290 has been marked as a duplicate of this bug. ***
Comment 4•23 years ago
|
||
My search for this bug failed because it was filed under the wrong component. My suggestion from bug 109290 is as follows: processmail, line 987ish $newcomments =~ s/(Created an attachment \(id=(\d+)\))/${showattachurlbase}$2\n$1/g;
Component: User Interface → Email Notifications
Comment 5•23 years ago
|
||
Maybe I'm just being nostalgic, but I actually like the attachment's description being on the line below the "Created an Attachment" message rather than on the same line seperated by a colon.
Updated•23 years ago
|
Priority: -- → P2
Target Milestone: --- → Bugzilla 2.16
Comment 6•23 years ago
|
||
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
Assignee | ||
Comment 7•23 years ago
|
||
Comment on attachment 57221 [details] [diff] [review] Put a "\n" in the comment instead of ": " Works, r=myk, no second review needed.
Attachment #57221 -
Flags: review+
Assignee | ||
Comment 8•23 years ago
|
||
Since this bug is a regression I have applied the fix to b.m.o. and am now testing it.
Assignee | ||
Comment 9•23 years ago
|
||
Checked in. Resolving fixed.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 10•22 years ago
|
||
fixing incorrect milestones on fixed bugs.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.16
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
•