| Summary | Attaching an empty file (0 bytes) fails with no feedback |
| Queue | DIMP |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | slusarz (at) horde (dot) org |
| Requester | chuck (at) horde (dot) org |
| Created | 08/17/2008 (6163 days ago) |
| Due | |
| Updated | 08/18/2008 (6162 days ago) |
| Assigned | 08/18/2008 (6162 days ago) |
| Resolved | 08/18/2008 (6162 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
http://cvs.horde.org/diff.php/dimp/templates/index/index.inc?r1=1.217&r2=1.218&ty=u
State ⇒ Feedback
display on the compose page, which has been fixed.
And we have previously discussed the '0 bytes attachment' issue
previously (although I couldn't find the discussion with a quick
search). IIRC the reason we don't allow 0 byte attachments is either
1.) it has something to do with the limitation of the PHP upload core
code and/or 2.) users uploading a file that may be in use on the
browser-side (i.e. a windows temp file) get instant notification that
the file they thought they have attached wasn't attached and/or 3.) we
couldn't think of a situation (outside of testing) why a 0-byte file
was valid.
http://cvs.horde.org/diff.php/dimp/js/DimpCore.js?r1=1.450&r2=1.451&ty=u
http://cvs.horde.org/diff.php/dimp/js/src/DimpCore.js?r1=1.450&r2=1.451&ty=u
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Attaching an empty file (0 bytes) fails with no feedback
Queue ⇒ DIMP
Assigned to Michael Slusarz
Milestone ⇒
Patch ⇒ No
State ⇒ Assigned
file isn't attached, and there's no feedback. Is there a reason we
would want to disallow attaching empty files? I know the use case for
it is questionable, but I don't see a real reason to disallow it either.