Documentation for a historical release of Infusion: 1.3
Please view the Infusion Documentation site for the latest documentation.
If you're looking for Fluid Project coordination, design, communication, etc, try the Fluid Project Wiki.

Uploader Wireframes (Error Handling)

Owned by James Yoon
Last updated: Jun 09, 2011 by Colin ClarkVersion comment
2 min read

Files added in queue, no errors

Files added in queue, client-side errors

In the event that there are client-side errors (i.e., errors that are detected on the client side before uploading is even attempted), error messages should appear in the general uploader status area (the area occupied normally by "To upload: x files (y MB)").

Currently, we're handling two types of client-side errors:

  • File is too big
  • Too many files

In each case, error messages should be provided in the general uploader status area. The files should not be added to the uploader queue. Additionally, users are given the facility to:

  • Clear individual error messages
  • Get more details on the error. In particular, the list of files that were not added to the uploader queue.

If, after receiving an error, the user successfully selects one more new files, the error messages should be removed and the extended status panel should recede. Similarly, upon upload, the error messages should be removed and the extended status panel should recede.

Files uploaded, server-side errors

In the event that there are server-side errors (i.e., errors that are detected on the server side during/immediately after uploading), error messages should appear in the file status area, for each offending file.

Currently, we're handling two types of server-side errors:

  • Connection error (network problem)
  • Rejection error (server logic)