The most important thing about the jAlbum 33.3 update is the fix for the uploader: jAlbum was sometimes re-uploading the whole gallery when resuming an interrupted upload. Here are more details on this matter:
If a user had a gallery upload interrupted due to network connection issues, then jAlbum would sometimes re-upload the whole gallery. This elusive problem has been around since day 1 but has now been addressed. If an upload is resumed after a connection breakdown, then jAlbum has to re-scan all files on the server in order to figure out where to resume the upload process. This re-scanning would break on some ftp servers and some albums in combination with the "ftp (edtftpj)" connection type. Affected albums are albums that are having a space in the directory name or where one of the parent directories contains a space. It turned out that the "ftp (edtftpj)" connection type was using the deprecated "LIST" command to list files instead of using the more modern (but less supported) "MLSD" command. The old "LIST" command wasn't accepting spaces in file names, but instead of complaining about it, returned an empty file list. This caused jAlbum to think that no files had been uploaded at all.
jAlbum 33.3 now contains logic to check the feature set of the ftp server when using the "ftp (edtftpj)" connection type. If the "MLSD" command is supported, it will be used instead of the LIST command, thus working around the problem.
It MAY be the case that a user encounters this problem even with v33.3. This could happen if the user uploads to an old ftp server that doesn't support the "MLSD" command. If jAlbum suspects this to be the case (seeing an empty result set when querying a folder containing spaces), then jAlbum prints a warning message to the system console and triggers a red triangle to show in the lower-right corner. If you ever see this, please report it to us for investigation!
(The user has always been able to traverse the directory tree via the user interface of the upload window. This has always worked because, instead of passing the path to list to the "LIST" command, jAlbum would change directory to the relevant directory and then list it without a path as argument. We avoid using that mechanism during uploads though in order to ensure that we don't rely on "current directory states" (relying on that can cause files to be uploaded to the wrong locations under certain circumstances))
