Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Wrong folder date when syncing #7009
First, I'm not sure if this is a core problem or a client (Windows) problem. I put it here since it's the same problem as issue #1897 (closed because it needed info).
The creation date of a folder should be the same in every computer after syncing.
After syncing, the date of a folder is different in each computer.
Steps to reproduce
Raspberry Pi running ownCloud with "version":"126.96.36.199" and "versionstring":"6.0.1".
One computer: Windows 7 64 bits
Hope you can have a look at this, at least to see if it's reproduceable. Thanks for your time!
csync never touched the creation date (of files or folder). The creation date is not even part of the property exposed by webdav.
For example, if one modifies a file on the server, it needs to be downloaded, but then a temporary files is created which change the modification time of the directory. Next sync we would then have to sync the modification date again. And that sounds wrong.
So because it was unreliable anyway, we stopped syncing the modification time of directories, saving time and bandwidth.
If having the modtime of the directory synced is soo important, we could add this feature back.
referenced this issue
Mar 17, 2014
referenced this issue
Sep 5, 2014
This was referenced
Feb 9, 2015
I’m closing this issue because it has been inactive for a few months. This probably means that the issue is not reproducible or it has been fixed in a newer version.
Please reopen if you still encounter this issue with the latest stable version and then please use the issue template. You can also contribute directly by providing a patch – see the developer manual. :)
This problem still exists in owncloud-8.2.1.
This is a show-stopping problem for some of our owncloud users. We may have to look at other solutions if this behaviour isn't changed in owncloud. Since we also have a seafile deployment I'll be testing for this problem on that platform. I'd hate to have to move our users from owncloud to seafile because of this one problem that seems like it should be quite trivial to solve, but that may be the result.
I understand the "by design" arguments above, but if possible I'd like to see this as a configurable option, if not always on. That is, for people who want to save sync time and bandwidth, they can disable directory mod time syncing. For all others, directory time mod syncing is on by default.
I'm following up on what I said in my previous post about testing for this problem in seafile. I've tested for this directory modification time issue in owncloud-8.2.2, seafile-5.0.4, and dropbox. It seems that at this time seafile is the only one of the three that properly preserves directory modification times.