FileZilla Forums

FileZilla does not remember file contents.

If you make local changes to the file and afterwards press F5 in FileZilla, does the file size and modification time in the local directory listing change?

I generally just drag and drop from explorer, but when that was failing I then tried to update the file using the local directory listing within filezilla and same problem happened.

Look, the fact is if you read my post thoroughly, you will see that unless I am lying, it is 100% a problem with filezilla caching files that don't exist anywhere else, for some odd, strange and weird reason.

As outlined - it is DELETED from the target, and the local is no longer the same as the old one, and when I upload that exact same filename, filezilla somehow magically manifests an older version that at that moment exists nowhere else.

Other ftp programs 30 seconds later update it fine. Different filename through filezilla, no problem.

I repeat:

botg wrote:FileZilla does not remember file contents.

I also repeat my question that hasn't been answered yet:

If you make local changes to the file and afterwards press F5 in FileZilla, does the file size and modification time in the local directory listing change?

Of
course
it
does.

What is your file exists action set to??

As previously mentioned, it works for other files, and therefore, by inference, the settings are correct.

And more relevantly, it happens even when the remote file is deleted.

Do you want to read my original post again and take more than 5 seconds to digest it so you ask me more pertinent questions?

Well, FileZilla does not cache file contents. It simply lacks the capability to do so. If you upload a file yet only an old version appears on the server, there can be only three options, in decreasing order of likelyhood:
1) Important facts have been omitted in the problem report
2) FileZilla is being presented an outdated file by the system
3) An utterly terrible transparent reverse proxy uploads a stale copy of the file

SSy1 wrote:And more relevantly, it happens even when the remote file is deleted.

Do you want to read my original post again and take more than 5 seconds to digest it so you ask me more pertinent questions?

Your attitude is brutal.
I see your functions.php, so guessing you are using wordpress - did you recently install a caching plugin?
You sure you didn't set a cache rule for your files to not expire?

I had that issue yesterday with overwriting pdf files - and my w3 cache setting for media included pdf files, so the browser was still serving the old file even though the new file was clearly uploaded.

Additionally, slightly different file sizes between local and remote copy do mean NOTHING if the file has been uploaded as ASCII Data Type. If you upload it as Binary type then file sizes match.

Imagine that today, hundreds if not thousands of devices and software programs operate between FileZilla and the server. Caching and malfunctions can occur in each and any of them. Yet, the user always tends to blame the first (or only) thing they can see.

If you didn't pay your electricity bill, you wouldn't blame your vacuum cleaner for not working, would you?

Your attitude is brutal.

In response to disrespectful attitude - see post sequence.

I see your functions.php, so guessing you are using wordpress - did you recently install a caching plugin?
You sure you didn't set a cache rule for your files to not expire?

Thank you for the suggestion - no, nothing of the sort. And I don't see how that could happen - when I delete the file from the theme folder, Wordpress gives a 500 meaning the file is gone. When I re-upload the new file, filezilla delivers the old one.

Additionally, slightly different file sizes between local and remote copy do mean NOTHING

Read original post thoroughly. File was tested, not file size compared.

1) Important facts have been omitted in the problem report

Maybe - that's why you need to ask pertinent questions.

2) FileZilla is being presented an outdated file by the system

My thoughts exactly, but how this is possible only you would know. Especially since this does not happen with other software (and never has in over 15 years of development).

3) An utterly terrible transparent reverse proxy uploads a stale copy of the file

Also possible, and very strange that it would be that file only. Again, why only filezilla?

What's the difference between this one file and every other file? There must be some difference.

7 years later same problem.

I've had this for ages, my solution: stop using filezilla.

Tried it today, uploaded a CSV file (drag and drop so they dont blame the editor, and this file has no web view so they dont blame the browser, im using SFTP no proxy, file exist is "overwrite" so thats not it), FZ said it was uploaded successfully but log said "File transfer skipped", old file was just sitting there mocking me.

used other clients, no problem on replacing files, maybe just maybe its your code

It has been successfully skipped in accordance to your configured file exist action. That's not an error.

Me Too!!! Pulling Hair Out!