Custom Query (8074 matches)
Results (319 - 321 of 8074)
|#10729||fixed||APPCRASH when connecting to a FTP site|
Windows 7 Pro 64bit. Program load fine it only crashes when you try to connect to a FTP site. Here is the error Problem signature:
I have used the program on other windows 7 64bit and never had this problem.
|#11495||outdated||APPCRASH when uploading images|
Thank you for the great software.
Lately I experience the following windows crash anytime I try to upload a list of images from my PC to the server:
Read our privacy statement online:
If the online privacy statement is not available, please read our privacy statement offline:
This happens after a couple of images have been successfully uploaded I have been using Filezilla for ages and never experienced the same issue.
|#401||APPE corrupts my work|
I want to use FileZilla to upload Files to a Server. I want FileZilla to insert Files to the remote Filesystem that does not exist on the Server so far. FileZilla asks me how to handle Files on my sytem that are older on the server. What FileZilla does not ask me - and does wrong - is handling files with an identical timestamp on my PC and the Server. I transfer ASCII-Files. On my system a linebreak is stored with 2 bytes. The remote system stores one byte per linebreak. It strips off the extra byte automatically, thus making the file shorter. FileZilla on an update of the whole directory structure recognizes the identical FileDate and the different (smaller) filesize and thus thinks it has to APPEnd extra bytes to the file on the server. That's why I'd call "motherfucking bullshit" ;-) It does not malke sense at all. My ASCII-files are PHP scripts that now become unparsable by PHP and screw up my whole system. It took me 3 houres yesterday (Sunday evening) to figure this error out, finally delete all files on the server and upload them wholly. So please change FileZilla that it works in a way it does not automatically corrupt my scripts.
Thank you, Bernhard