FileZilla Forums

I'm trying to switch to Filezilla from FireFTP as a my FTP client. I use FTP primarily to connect to my servers and edit files there. FireFTP allows instant upload of changed files, so as soon as I save changes in my text editor - file's uploaded to the server and I can test it. I see that FileZilla is capable of watching files, but it does three things that make it hard to work with it:

1) it takes 8 seconds to recognize that file has changed,
2) asks to upload the file - I need this to be automatic,
and
3) asks to overwrite a temporary file when opening same file from the server for editing.

How can I bypass these two prompts and make it upload instantly?

You cannot bypass these prompts.

I see. Good thing there's at least FireFTP, then!

Now, I am using winscp application instead of filezilla, just because it does not ask for prompt. Getting prompt to see the changes is very annoying, to see the changes you have to switch 3 times(the editor, then filezilla and then browser) . If filezilla support instant automatic uploading I would gladly switch to it. This is the only reason I registered to its forum.

The prompts are here to stay. That has been said numerous times. Impossible to detect when an external editor has really finished saving. Other programs guesstimate and thus will be prone to data corruption, eventually.

We know this creates inconvenience, but isn't the health of your data more important?

Sorry for bringing this topic up again, but Filezilla already knows when a file is saved by the user, and we just want the file to upload without asking for confirmation. The app has options for this but this options simply doesn't work. Here's a printscreen for reference (https://prnt.sc/ZV2Op7qU988h). I have tested all this options. And no matter what, Filezilla always asks for action. This is not something from another world and should be working.

Filezilla already knows when a file is saved by the user

No, it doesn't. It just detects that a file has been touched (modified or otherwise updated), but it doesn't know if and when the editor is done saving. That's impossible to detect as the editor is an external tool and won't provide any feedback.
Your assumption might work with editors doing linear saving (from top to bottom in one atomic action). It will fail if the editor is doing chunked saving (saving changed segments of a file, opening, updating and closing it multiple times). Usually, editors able to handle big files use that method (paging in an out file segments instead of loading the whole file into memory).
Imagine FileZilla starting to upload right after the first chunk of many has been saved. The remote copy will not contain all changes or be otherwise corrupted. Plus, the local saving of the file will also be interrupted, with FileZilla blocking the file handle.

It's unfortunately not as easy as many users think, not grasping the complexity of handling external tools. Automatic save detection only works with internal editors, where there is communication and feedback between the components.

Sorry for bringing this topic up yet again, but this thread is a top result when googling the issue. FileZilla is a great program overall, and I'm grateful it exists, but the safeties disrupt my workflow so dramatically that I can't keep using it. I'd rather pull out my old Windows laptop with WinSCP installed. Is WinSCP's auto-upload capability known to corrupt files?

We know this creates inconvenience, but isn't the health of your data more important?

Personally, no, it isn't. I have backups. If I was given an option to bypass any safety mechanisms and automatically upload, I would happily use it. Even if I had to agree to a prompt that said "hey, you're doing something dangerous, are you sure?" - Or if the capability was limited to relatively small files which are unlikely to be modified in chunks.