WEBDAV-server problem

[Franz47]

I have started to test Freefilesync whether it works for my purpose, which is using a Nextcloud-Webdav-server in the internet and synchronize its contents with several PCs whenever I use one of them. So I have all files up to date whenever I start working an any of the PCs.

I mapped the Webdav-server as a drive in Windows, no problem. I created a folder on the PC and a job in Freefilesync for these two. Then I copied files into the PC folöder, synchronized, worked ok. I could find these files on the mapped drive on the PC and on tWEBDAV-server when checking via Webinterface. I checked the files and saw that as a result of the synchronisation the files on the PC had retained the original time stamp, the files on the mapped network resource had the date of the copying process.

Then I deleted one file on the PC and tried to sync again. Now I get a conflict notice about this file in the file comparison and when trying to sync I get an error message that the files had been changed since the last synchronisation and therefore are not synced. I definitely had not done anything with this file after synchronizing except deleting it.

I was suspicious about the file time stamps and checked. When copying a file from a Windows folder into the mapped drive, the timestamp remains as in the original file and the file is copied to the server. When a file is synchronized from the PC-folder to the mapped network drive, it reveives the current time stamp. So that change must be done by Freefilesync. I searched for a switch to force retainment of the file date without success.

Then I created a sync job between two folders on the PC, then the file dates were retained during the synchronisation.

Any idea to solve this problem?

[therube]

I know nothing of it, but it seems, neither do they ;-), https://github.com/nextcloud/server/issues/15192.

[Zenju]

The next version implements some changes with regards to file time handling during copy. It might also "solve" the time stamp issue discussed:
viewtopic.php?t=10263&start=30#p39776

[Franz47]

It must be Freefilesync which changes the timestamp. When I copy manually a file from a folder to the mapped drive, it retains the date of last change, which is the criteria upon which it should be decided whether the newer file should override the older version on the server or vice versa.

The date of creation is of course different, depending on when the file was copied to the folder or mapped drive.

Freefilesync only says "date" but does not take into account that the file has several "dates". Maybe comparison of "date of last change" should be a choice when configuring comparing?