Opened 13 years ago

Last modified 4 years ago

#5617 new Bug report

preserve timestamps option not working on directories.

Reported by: jerome Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc: rodlockwood@…
Component version: Operating system type: Windows
Operating system version: Windows 7 SP1 32 bit



when the preserve timestamps is enabled,
and when uploading a directory with some sub directories inside, the existing directories of my local filesystem are not modified.
(of course it's ok for my files as filezilla is a great app, developped by great guys)

it's not a big deal..

but maybe an option could be added for the timestamp option :
'ignore directories timestamp'
in some case it would be very helpful for my eyes and my backup/restore ops.

kind regards,

Jerome fr

Attachments (1)

Filezilla version.PNG (15.9 KB ) - added by tmcmilli 10 years ago.
Help, About Filezilla (version number)

Download all attachments as: .zip

Change History (5)

comment:1 by Rod Lockwood, 12 years ago

Cc: rodlockwood@… added

I am using Filezilla 3.5 and I have noticed the same problem. It is because the folder is "created" not copied. So the time stamp is different. There is another suggestion to add a "touch" feature to reconcile the difference in time stamps, but this would probably be easier.

And it does create a problem. You have the Default overwrite files action set to "overwrite if source file is newer". I have noticed that if you are uploading/downloading an entire folder, and the source folder is newer, the target files will still be overwritten even if the contents of the source folder are older.

by tmcmilli, 10 years ago

Attachment: Filezilla version.PNG added

Help, About Filezilla (version number)

comment:2 by tmcmilli, 10 years ago

Operating system version: xpWindows 7 SP1 32 bit
Priority: lownormal

This issue of timestamp preservation not working is still an issue with the very latest version of Filezilla. The current date and time are stamped to the transferred file rather than the original date and time being preserved. The option to preserve is in fact set on Filezilla and it does not work. See Filezilla and Windows OS versions below from Help, About in Filezilla.

FileZilla Client


Build information:

Compiled for: i586-pc-mingw32msvc
Compiled on: x86_64-unknown-linux-gnu
Build date: 2014-02-11
Compiled with: i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2)
Compiler flags: -g -O2 -Wall -g -fexceptions

Linked against:

wxWidgets: 2.8.12
GnuTLS: 3.1.11

Operating system:

Name: Windows NT 6.1 (build 7601, Service Pack 1)
Version: 6.1
Platform: 32 bit system

comment:3 by Hubert Schölnast, 7 years ago

I understand, that preservation of timestamps of directories can be problematic. But if this problem can't be solved, then please at least add an additional option to Directory comparison to make it able to compare only timestamps of files, but not of directories.

I always work with this settings:

View - Synchronized browsing = checked
View - Directory comparison - Enable = checked
View - Directory comparison - Compare modification time = checked

I wish to have an additional option:

View - Directory comparison - Compare modification time of directories

And please rename "Compare modification time" to "Compare modification time of files"

Because then I can set:

View - Directory comparison - Compare modification time of files = checked
View - Directory comparison - Compare modification time of directories = not checked

The reason for my wish:
When I can't have identical timestamps for directories, I don't wont to have directories highlighted at all. I already know, that they have different timestamps, but what is this information good for, when I can't do anything to correct it?

But I still consider this solution as a plan B workaround. Better than nothing, but still worse than plan A.

I would still strongly prefer plan A: Have identical timestamps on my ubuntu-server and my local iMac.

comment:4 by Johnny, 4 years ago


+1 for Hubert's request.

Please only highlight a folder color if a file within that folder is out of sync.

At least that would give a user indication as to whether the remote/local directories are truly out of sync without having to drill into the directory.

Otherwise, it's not providing actionable information.

Thanks in advance for considering this!

Note: See TracTickets for help on using tickets.