Problem when uploading files that are begining with a blank space.

[Le_Bug]

Hi,

Yummy FTP is a very good FTP client.
I used it from about two or three day, but I will buy it soon.

I think there is a bug on file upload.
When I try to upload a file called " inconnu.jpg" Yummy FTP don't upload it.
I've got this alert :


When I try to rename a file "inconnu.jpg" to " inconnu.jpg", the file is deleted.

Am I the only one with this problem ?

(I know, people who named theirs files with blank space are stupid :p)

[JD]

I've just tested this and had no problems whatsoever.

The error message you're getting is not from the upload itself (which was successful) but from the setting of permissions on that file after it was uploaded. So it sounds to me that your server does not work well with files that start with a space character.

I also tried renaming the file both in the Mac listing and the Server listing (you did not say which) to remove the space character at the beginning. The file was not deleted, but it did reposition itself lower down in the listing because the listings are sorted alphabetically. I think you assumed that the file was deleted, when in fact it simply moved lower down in the list and out of view.

I will need to see an FTP Transcript from you showing this problem occurring. That way I can be certain that my diagnosis is correct. Please ensure that you enable the 'Log all connections' checkbox in the Transfers tab of the Preferences first, then perform your transfer. Select 'Save FTP Transcript' from the File menu and send the transcript file to me by email at the support email address.

Are you the only one with this problem? All I can say is that nobody else reported such problems, and certainly, using file/folder names that start with a space character is never a good idea

[Le_Bug]

You're right.

The file is not deleted.

Some servers accept file whith space, some else no.
They're renaming the file after de STORE cmd (Like "_iconnu.jpg").
I did'nt see that before.

There's no problem, but the CHMOD failled because the file was renamed.

Code:

CWD /usr/local/apache/vhosts/devbug.net/htdocs
250 CWD command successful
TYPE I
200 Type set to I
PASV
227 Entering Passive Mode (82,112,100,163,248,10).
STOR  none.jpg
150 Opening BINARY mode data connection for  none.jpg
226 Transfer complete.
CWD /usr/local/apache/vhosts/devbug.net/htdocs
250 CWD command successful
SITE CHMOD 775  none.jpg
550 none.jpg: No such file or directory
CWD /usr/local/apache/vhosts/devbug.net/htdocs
250 CWD command successful
PWD
257 "/usr/local/apache/vhosts/devbug.net/htdocs" is current directory.
TYPE A
200 Type set to A
PASV
227 Entering Passive Mode (82,112,100,163,249,94).
LIST
150 Opening ASCII mode data connection for file list

Manualy I send this RAW cmd:

Code:

SITE CHMOD 775 "\ none.jpg"

Works fine.

But on another server with the same file:

Code:

CWD /decoupe
250 OK. Le repertoire courant est /decoupe
TYPE I
200 TYPE est maintenant 8-bit binary
PASV
227 Entering Passive Mode (193,252,114,11,195,159)
STOR  none.jpg
150 Connexion de donnee acceptee
226-208877.1 Moctets d'espace disque libre
226-Fichier transfere sans probleme
226 0.242 secondes (mesuree ici), 34.57 Koctets par seconde
CWD /decoupe
250 OK. Le repertoire courant est /decoupe
SITE CHMOD 775  none.jpg
550 Ne peut changer les permissions vers none.jpg: No such file or directory
CWD /decoupe
250 OK. Le repertoire courant est /decoupe
PWD
257 "/decoupe" est votre position actuelle
TYPE A
200 TYPE est maintenant ASCII
PASV
227 Entering Passive Mode (193,252,114,11,195,160)
LIST
150 Connexion de donnee acceptee

But the stored filename is "_none.jpg".

So, the CHMOD failed again.

I don't think that is there a prety solution at that.
Testing if the file exist befoire doing the chmod ? Too long when there are many files.
Don't show the alert ? Why not, but real errors will not be show.

Ok, I know why this alert comes up, I will do with this

Thanks for your reply.

Le_Bug.

[JD]

Thanks for coming back with this information. It's useful for me and for others.

I don't think there is really a very good solution to this that can be implemented in Yummy FTP. It's possible to enclose the name in quotes for the CHMOD, like SITE CHMOD 775 " filename.jpg" but this is not a standard and it's likely that other servers will reject this format.

The only solution that will work with all servers is to stop using spaces at the beginning of names.

[Le_Bug]

I'm agree with you, I nerver used spaces.
It's jsut one of my client who decide to name some of his website's images with space.
I was very surprised of that

I will tell him to not doing that again