We’ve gotten lots of great feedback and a few bug reports from users testing the first Jungle Disk 2.0 beta released last Friday. We’re happy to announce an updated version of the beta is now available that fixes a number of these issues and adds a few new features as well. We highly recommend all beta users update to this new release. You can download the new version from our beta downloads page, and see the full list of features and fixes in the release notes. Of note in the “new features” – we’ve added support for the official Amazon S3 fast file copy feature which is now in beta. This feature removes the need to use our own EC2 servers for copying and renaming files. Jungle Disk now uses this feature when upgrading buckets as well, which should make the bucket upgrade process faster and smoother. Finally, it also allows European S3 users to copy and rename files quickly rather than re-uploading as had previously been required.

There are several important bugs that were fixed in this release that we want to call attention to, in case current beta users have run into them:

• If you create a new Jungle Disk 2.0 bucket and enable High Security and Encrypted Filenames, but do not set a bucket password, then later go into the configuration and set a bucket password, your existing filenames may display incorrectly. This issue may not become apparent until you delete you directory cache.
• Similarly, if you create a new Jungle Disk 2.0 bucket, or upgrade a Jungle Disk 1.0 bucket and enable High Security and Encrypted Filenames with a bucket password, then later disable the bucket password, your existing filenames may display incorrectly. Setting a new bucket password again will correct the issue (as will upgrading to this beta release).
• If you upgrade a Jungle Disk 1.0 bucket with a custom encryption key but do not enable High Security on the Jungle Disk 2.0 bucket your previous custom encryption key may not be imported properly into the new bucket configuration. You can fix this by using the “Manage decryption keys for upgraded Jungle Disk 1.0 buckets” link in the Encryption settings (note: you must set a bucket password for this link to appear). In 1.99b these keys are imported correctly when upgrading a 1.0 bucket.
• If you open the Advanced Options in the Backup Selection dialog on Windows it may set your Backup Path for the current directory to an illegal value (ending in a backslash). The new version will correct this automatically, but if you backed up with the incorrect path you may see a directory name on your Jungle Disk with a backslash in the name. You can use the local web interface to delete the incorrect directory.