[Bug 32646] New: If attachment is too large on new bug, new bug will be posted without error message

http://bugs.winehq.org/show_bug.cgi?id=32646

Bug #: 32646
           Summary: If attachment is too large on new bug, new bug will be
                    posted without error message
           Product: WineHQ Bugzilla
           Version: unspecified
          Platform: x86
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: bugzilla-unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]
    Classification: Unclassified

While trying to add a new bug and an attachment which is over the size limit,
the attachment will not be added, but no error message is initially shown
except when trying to reupload the file.

[Bug 32646] If attachment is too large on new bug, new bug will be posted without error message

http://bugs.winehq.org/show_bug.cgi?id=32646

--- Comment #1 from Austin English  2013-01-06 22:00:34 CST ---
Likely an upstream bug.

[Bug 32646] If attachment is too large on new bug, new bug will be posted without error message

http://bugs.winehq.org/show_bug.cgi?id=32646

Ken Sharp  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from Ken Sharp  ---
That's not the case: the bug is logged and an error message is displayed saying
that the attachment was discarded.

Bugzilla has just been updated and the behaviour has not changed.

"The bug was created successfully, but attachment creation failed. Please add
your attachment by clicking the "Add an Attachment" link below."

[Bug 32646] If attachment is too large on new bug, new bug will be posted without error message

http://bugs.winehq.org/show_bug.cgi?id=32646

Ken Sharp  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #3 from Ken Sharp  ---
Closing