Ok. I have found this option, which has solved my immediate problem, but I think there should be a better way of handling files in 'folders' created by other programs. (NB I am aware that S3 doesn't support folders and each program is simulating them).

I was looking for a file that I was fairly sure I had uploaded to S3 but couldn't find. It was complicated by the fact that I wasn't 100% sure of the filename. I spent a bit of time going through all buckets, but almost gave up. It only took about a minute to find it once I realised that BE was not showing all the files when in folder view and switched back to show full paths.

When in Folder view, if BE encounters a filename containing a / it assumes it is in a folder, but if it can not find the folder then it could, either add the folder to its list of folders dynamically or else display the file with the full name (as it would when not in folder view). I think the first option would be preferable, but in might raise problems with users attempting to edit items that don't really exist.

However at the moment the files simply don't appear which is bad. Some of my buckets will be used by other people to upload files, and I since can't force them to use BE, I might come across this problem again.

Can this be changed?

Also the wizard that comes up when you select 'Create folders for backward compatibility' could do with a little more explanation or a help button. I sorted guessed it would do what I wanted, but wasn't sure. (I tried it out on a test bucket to make sure). I couldn't find any details about this on your website/forum. (Couldn't find any way to search either of them, which is another issue)


Stephen

Thansk for your feedback. This was addressed in June release. We have made some more improvements in the most recent beta (sept 2008). We o longer need virtual folders to display files which have "/" as part of the file name. You can download the latest beta from links posted in this blog post:

http://blog.bucketexplorer.com/2008/09/ ... l-release/