Inverse of timezone offset not applied when setting remote file timestamps
|Reported by:||Howard Brown||Owned by:|
|Component version:||3.18.0||Operating system type:||Windows|
|Operating system version:||8.1|
I want to transfers files up to my server that are actually newer than the version that is on the server. So I set the Preserve timestamp of transferred files and adjusted the server timezone offset to 3 hours, and enabled the directory comparison feature to use the compare modification time option.
To test this I created a new file on my computer in the root of the local directory that is synced with the server's site root directory and then refreshed the local window to show the new file.
The new file did not show with the yellow highlight.
I uploaded the new file and after it was copied to the server the version on the server had the same time as the local file plus three hours, but the file on the server was green highlighted indicating that it was newer than the version on my computer, which was just updated and except for the timezone difference was actually the same time.
I thought that the server timezone offset was supposed to take care of this kind of issue.
So two things:
1) Before the local file existed on the server, why wasn't it yellow highlighted in the local window?
2) After the local file was created/copied onto the server, why was it green highlighted in the server windows?
P.S. Some programs allow you to highlight and copy the version and other information contained in the About pop-up window, which helps when filling out trouble reports. You have a 'send to clipboard' function which is nice, but being able to copy the individual fields is also very helpful.
Change History (5)
follow-up: 4 comment:1 by , 7 years ago
|Summary:||With the server timezone offset to 3hr, after uploading a file to the server show the file as newer than the one just uploaded. → Inverse of timezone offset not applied when setting remote file timestamps|