We have fixed some issues and improved some existing features:
- Fixed: The JavaScript error below which occured only on IE 8 (it didn't occur in IE 8 compatibility mode of IE 9):
"HTML Parsing Error: Unable to modify the parent container element before the child element is closed (KB927917)"
- Fixed: Incomplete/corrupted downloads problem in zip streaming feature (first introduced in v4.5.0) which occured when downloading large files due to a timeout issue.
The problem did not occur with single file downloads. Note that zip streaming is active only when multiple items are downloaded or "Download As Zip" action is used explicitly.
Previously suggested web.config workaround (executionTimeout setting) will not be necessary after this fix so it should be removed.
- Fixed: Streamed zips (even small ones) could not be opened/unzipped with Archive Utility on Mac, the zip file structure is fixed to be compatible with this utility.
Note that when the size is larger than 4GB, zip file must be generated in zip64 format instead of the regular format.
Some older unzippers like Windows XP Explorer and Mac Archive Utility (maybe not newer versions) do not support zip64 format so you may need to use
a more recent unzipper (Mac Unarchiver, Winzip, Winrar etc.) for files larger than 4GB on these systems.
- Improved: Zip files will be generated with no compression (files are stored) during zip streaming so that CPU usage is minimized.
There are two additional advantages due to this improvement other than server performance.
First advantage is, we can simulate the zip generation and determine the zip file size exactly (and fast) before streaming.
This was not possible previously so the browser showed indeterminate progress information (chunked transfer encoding) during download due to lack of knowing the final file size.
So now the browser will show the exact zip file size on its "Open/Save As" dialog immediately after user clicks "Download As Zip" and
it will show a determinate progress information on "Downloading" dialog. In short, zip streaming will behave exactly like single file downloads.
Second advantage is, the users will be able to extract the received zip file very fast as there is no compression. This would be helpful when downloading large files and folders.
Users who want to actually compress files should use "Add To Zip" action instead of "Download As Zip" and then download the generated zip file.
- Fixed: Some unnecessary errors were being recorded in the event log when the download was interrupted mostly due to user cancelling the download.
- Improved: On Upload dialog, Ajax and Flash menu items will be disabled on the main context menu's submenu "Upload Method" when these methods are not available to prevent confusion for the user.
Flash menu item will be disabled when Adobe Flash Player is not found or enabled in the browser. Also "Add" button will be enabled only when Flash object is loaded completely to prevent user clicking
the button too early. Ajax menu item will be disabled when the application is running on ASP.NET medium trust which does not allow Ajax upload method. Note that these upload methods were already disabled
and degraded to the next best method when not available. This improvement is only for UI to report the available upload methods to the user correctly.
- Improved: For security reasons, maxAllowedContentLength and maxRequestLength settings will be increased to 2GB only for the upload handler in "FileUltimate/Web.config" file.
The default IIS and ASP.NET limits is sufficient for other handlers so keeping them at default values will protect against DoS attacks.
- Changed: Renamed resource folders under App_GlobalResources from FileUltimate and FileVista to FileUltimateResourceStore and FileVistaResourceStore.
----------------------------------------------------------------------------------------------------------------------------------
Instructions for applying the fix:
- Please download the fix package:
Fix 2 for FileVista v4.5- Copy and overwrite all the files from the package to your FileVista installation. If you modified the default FileVista\Web.config file before then you should move your custom settings to the new file that will replace it.
- Rename resource folders under FileVista\App_GlobalResources from FileUltimate and FileVista to FileUltimateResourceStore and FileVistaResourceStore.
This is a cumulative fix (includes Fix 1 - 4.5.1). This fix is included in the v4.5.9 download packages as of writing this message. Users who will download the product after today, do not need to apply the fix.