Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing implementation of timestamp feature to set modification date on uploaded files #10171

Closed
cyberduck opened this issue Dec 8, 2017 · 6 comments
Assignees
Labels
bug fixed onedrive version:6.3.1
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Dec 8, 2017

27aeff2 created the issue

In Cyberduck and Mountain Duck, the date created field is reported as the date modified field rather than the date modified field. This means that you cannot use synchronization software which depends on timestamps, such as FreeFileSync. This is not a defect in Cryptomator in this case, as opening the same vault in Cyrptomator from OneDrive Files On-Demand in Windows 10 produces the expected result. A comparison image and the version numbers tested are attached. As an example, the first file (3.8MB) was added to the vault on 12/6 but was actually last modified on 11/27


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 12, 2017

@dkocher commented

Currently modification dates of files uploaded to OneDrive are not preserved regardless of the Cryptomator vault. For other protocols, make sure to have Preferences → Transfers → Timestamps → Uploads → Preserve modification date checked.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 13, 2017

27aeff2 commented

That option only appears to be available in Cyberduck, but not Mountain Duck

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 13, 2017

@dkocher commented

In Mountain Duck, timestamps are set depending on the application that is writing files and updating attributes. There will be a fix in version 2.2.1 that timestamps were not always applied correctly.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 29, 2018

@AliveDevil commented

Thanks for pointing out.
Reported dates were those of OneDrive keeps internally for creation and modification dates. We have performed necessary steps to implement the timestamp feature for OneDrive component.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 29, 2018

@dkocher commented

In b58108c.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 2, 2018

@dkocher commented

Milestone renamed

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug fixed onedrive version:6.3.1
Projects
None yet
Development

No branches or pull requests

2 participants