3.35.1 bug: deleting file on server doesn't really refresh the directory content
Moderator: Project members
3.35.1 bug: deleting file on server doesn't really refresh the directory content
Load a server directory in FileZilla that contains at least one file (file xy)
Copy or move another file there without using FileZilla (file zzz)
Delete file xy
While it now looks as if FileZilla does refresh the view, file zzz does not become visible. Only a manual use of F5 reveals what's really there.
It works correctly when you do the same with a local directory, so it would be cool to get the server side fixed. Thanks!
Copy or move another file there without using FileZilla (file zzz)
Delete file xy
While it now looks as if FileZilla does refresh the view, file zzz does not become visible. Only a manual use of F5 reveals what's really there.
It works correctly when you do the same with a local directory, so it would be cool to get the server side fixed. Thanks!
Re: 3.35.1 bug: deleting file on server doesn't really refresh the directory content
Not a bug, this is intentional.
Re: 3.35.1 bug: deleting file on server doesn't really refresh the directory content
Then I kindly request an option to get the same behavior for local and remote files.
Re: 3.35.1 bug: deleting file on server doesn't really refresh the directory content
Since refreshing the remote file list is slow by virtue of being remote, the local file list would need to be made slow as well.
Re: 3.35.1 bug: deleting file on server doesn't really refresh the directory content
Hmm..... I don't understand why "the local file list would need to be made slow as well".
Most of the time I use my NAS on the local side, and the remote list refreshes faster than the NAS (and about as quickly as C:)
Most of the time I use my NAS on the local side, and the remote list refreshes faster than the NAS (and about as quickly as C:)
Re: 3.35.1 bug: deleting file on server doesn't really refresh the directory content
Well - you wanted the same behavior for both sides, didn't you? Remote locations are usually magnitudes slower than the local lists.Hmm..... I don't understand why "the local file list would need to be made slow as well".
Please note that having a NAS on the local side is considered cheating if you didn't install FileZilla directly on the NAS. Network shares are slow by design.
No support requests over PM! You will NOT get any reply!!!
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
Re: 3.35.1 bug: deleting file on server doesn't really refresh the directory content
Maybe we talk at cross purposes here... I still don't understand why "the local file list would need to be made slow as well" - why not have "auto-refresh the server side after deleting" as an option and then it refreshes as quickly as it does, even if it's a bit slower than the local files?
I don't experience the "magnitudes slower" here - the server side takes only about twice as long to refresh as the C: SSD. And since it's considered cheating I'll try not to mention the NAS again.
I don't experience the "magnitudes slower" here - the server side takes only about twice as long to refresh as the C: SSD. And since it's considered cheating I'll try not to mention the NAS again.
Re: 3.35.1 bug: deleting file on server doesn't really refresh the directory content
Refreshing the remote file list can take several minutes. It is not feasible to unconditionally refresh it after every action.
Re: 3.35.1 bug: deleting file on server doesn't really refresh the directory content
I see... So if such servers exist, "auto-refresh the server side after deleting" needs to be an option.