Known issues in v1-1

History Key

  • New content
  • Removed content

Recent Versions

Choose two versions to compare, or click the link to view it.

  1. 6. 7 months by xjansen
  2. 5. 7 months by meijer
  3. 4. 7 months by meijer
  4. 3. 7 months by meijer
  5. 2. 7 months by meijer
  6. 1. 7 months by meijer
 

Under development, need to go through each issue to check whether it is an issue in filesender 1.1!  Red background means up no longer an issue in 1.1.  Yellow means still an issue in 1.1.  Purple means "busy checking".  Stuff that is checked is no longer in yellow background.  Green means "new known issue".  Colours to be removed when all checks are done.

FileSender 1.1 contains a number of known issues that we were unable to fix before releasing.  These issues typically are a consequence of certain architectural decisions or deficiencies in technology we depend on.  The majority of these issues are annoying but not show stopping.  

  1. Uploads larger then 2GB do not work on Linux and Mac OSX.  The Google Gears plugin no longer works properly on these platforms.  See bug tickets #176 ">2Gb upload on MacOS hangs at ~2Gb (Gears enabled) and #290 "File select fails in Linux/Gears for files of 2G or more".
  2. In the same browser session, when downloading the same file more than once using the same url or directly from the MyFiles table the download email notifications are only generated for the first download.  See bug ticket #356.
  3. The subject and message fields do not clear after cancelling an upload if a user authenticated using an upload invitation voucher.  The fields do get properly cleared when using standard authentication.  See bug ticket #357.
  4. UTF8: when using Gears some special characters are not properly displayed in the GUI.  See bug ticket #358
  5. UTF8: when downloading a filename with international characters other than ISO-8859-1 it will look 'funny' but fully usable when downloaded with IE.  See bug ticket #374
  6. When a user starts downloading a file, and then cancels the download, a "user has downloaded the file" email is still generated.  See bug ticket #307
  7. When a user has downloaded a file, the download page is accessible until the user's local browser cache is cleared or the file is deleted on the FileSender server.  This is a consequence of the choice to rely on a unique URL for authenticating users to downloads.  See bug ticket #187.
  8. 'My Files' listing and Bcc issues when uploading using a voucher and being authenticated as another user than the voucher issuer. See bug tickets #553 and #554.
  9. Problematic downloads using Chrome on Windows7-without-SP1.  See bug ticket #588.
  10. <Note: Xander has applied the Arnes patch to fix this to the 1.1 code.  That ought to remove this issue.>  Compare of UID attribute with admin uid broken when attribute is not in an array. See bug ticket #563.