no error message when file path is too long

[Eric]

I was trying to upload a file and nothing happend.
I did the upload by dragging the file from left to right.

I later found out it had to do with the complete filename and path.
It was too long. After making it shorter, I could upload by drag and drop.

It would be nice if there was some message about this.

There is a message when you upload with context menu item UPLOAD but not with drag and drop.

[Tim Kosse]

What's the complete filename including path of the file you are trying to transfer?

What is the exact error message you get when using the context menu?

[Eric]

Replying to codesquid:

What's the complete filename including path of the file you are trying to transfer?

What is the exact error message you get when using the context menu?

I have added the NZB file of the show I downloaded with NewsLeecher.
Newsleecher automatically extracts it.

Error message:

14:56:38: can't open file 'M:\alt.binaries.multimedia\[225663]-[FULL]-#a.b.teevee@EFNet-[ Gold.Rush.S05.Pay.Dirt.Special.Colossal.Clean.Up.720p.HDTV.x264-W4F ]- gold.rush.s05.pay.dirt.special.colossal.clean.up.720p.hdtv.x264-w4f\gold.rush.s05.pay.dirt.special.colossal.clean.up.720p.hdtv.x264-w4f.mkv' (error 0: the operation completed successfully.)
14:56:38: can't open file 'M:\alt.binaries.multimedia\[225663]-[FULL]-#a.b.teevee@EFNet-[ Gold.Rush.S05.Pay.Dirt.Special.Colossal.Clean.Up.720p.HDTV.x264-W4F ]- gold.rush.s05.pay.dirt.special.colossal.clean.up.720p.hdtv.x264-w4f\gold.rush.s05.pay.dirt.special.colossal.clean.up.720p.hdtv.x264-w4f.mkv' (error 0: the operation completed successfully.)
14:56:38: can't open file 'M:\alt.binaries.multimedia\[225663]-[FULL]-#a.b.teevee@EFNet-[ Gold.Rush.S05.Pay.Dirt.Special.Colossal.Clean.Up.720p.HDTV.x264-W4F ]- gold.rush.s05.pay.dirt.special.colossal.clean.up.720p.hdtv.x264-w4f\gold.rush.s05.pay.dirt.special.colossal.clean.up.720p.hdtv.x264-w4f.mkv' (error 0: the operation completed successfully.)
14:56:38: can't open file 'M:\alt.binaries.multimedia\[225663]-[FULL]-#a.b.teevee@EFNet-[ Gold.Rush.S05.Pay.Dirt.Special.Colossal.Clean.Up.720p.HDTV.x264-W4F ]- gold.rush.s05.pay.dirt.special.colossal.clean.up.720p.hdtv.x264-w4f\gold.rush.s05.pay.dirt.special.colossal.clean.up.720p.hdtv.x264-w4f.mkv' (error 0: the operation completed successfully.)
14:56:38: can't open file 'M:\alt.binaries.multimedia\[225663]-[FULL]-#a.b.teevee@EFNet-[ Gold.Rush.S05.Pay.Dirt.Special.Colossal.Clean.Up.720p.HDTV.x264-W4F ]- gold.rush.s05.pay.dirt.special.colossal.clean.up.720p.hdtv.x264-w4f\gold.rush.s05.pay.dirt.special.colossal.clean.up.720p.hdtv.x264-w4f.mkv' (error 0: the operation completed successfully.)
14:56:38: can't open file 'M:\alt.binaries.multimedia\[225663]-[FULL]-#a.b.teevee@EFNet-[ Gold.Rush.S05.Pay.Dirt.Special.Colossal.Clean.Up.720p.HDTV.x264-W4F ]- gold.rush.s05.pay.dirt.special.colossal.clean.up.720p.hdtv.x264-w4f\gold.rush.s05.pay.dirt.special.colossal.clean.up.720p.hdtv.x264-w4f.mkv' (error 0: the operation completed successfully.)

[Tim Kosse]

On Windows, the maximum length of filenames, including the full path and the terminating NULL, is limited to 260 characters.

While it is possible to circumvent this using the
?\ prefix for some API functions, doing so is dangerous as it disables safety checks and can be used to create files other programs cannot handle, e.g. it is possible to create files undeletable by Explorer.
Unless Windows itself gets fixed to handle filenames of such length, support for it won't be implemented in FileZilla either.

I recommend that whatever program on your system created these overly long filenames should be configured or fixed to shorten the filenames.

[Eric]

I didn't report this for a fix to keep the long file names, I just would like to see a dialog message telling me why the file is not uploaded instead of doing nothing and let me find out some other way.