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

Jump to bottom

server is seven time zones ahead: recently edited files sync the wrong way #12312

Closed
cyberduck opened this issue May 3, 2006 · 2 comments
Closed

server is seven time zones ahead: recently edited files sync the wrong way #12312

cyberduck opened this issue May 3, 2006 · 2 comments
Assignees
@dkocher
Labels
bug core duplicate high priority
Milestone
3.0

Comments

@cyberduck
Copy link
Collaborator

1305581 created the issue

A file placed in the local Cyberduck folder and sync'ed to the server is given the time stamp on the server which, in my situation, is seven hours ahead. If I edit the local file a few minutes later (actually anything less than seven hours later) and sync, the server file overwrites the local file containing my changes. I don't see anything in Preferences to give CyberDuck an offset time.

Sincerely,

Bob
@cyberduck
Copy link
Collaborator Author

@dkocher commented

This is a known issue which will be addressed in 2.6 See #12309 and #12198.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone 2.8 deleted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dkocher dkocher

Labels
bug core duplicate high priority
Projects
None yet
Milestone
3.0
Development

No branches or pull requests
2 participants
@dkocher @cyberduck