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

not synchronising modified files #1189

Closed
cyberduck opened this issue Jul 25, 2007 · 4 comments
Closed

not synchronising modified files #1189

cyberduck opened this issue Jul 25, 2007 · 4 comments

Comments

@cyberduck
Copy link
Collaborator

55f8b93 created the issue

I have a complete copy of my entire web server on my local hard disk. In earlier versions of Cyberduck, I could just synchronise the server root with my local directory, and the changed files would be uploaded without trouble.

The version of Cyberduck I use now (most recent) only synchronises the files in the top server directory - and it does so regardless of whether those files have been modified at all. A modified file in a subdirectory however is not synchronised.

I have marked this as major since it's far beyond "normal" to manually upload changed files when you actually have a synchronisation feature that is supposed to be working properly.

@cyberduck
Copy link
Collaborator Author

shoestring commented

I'm finding new files are recognised and uploaded in subdirectories, it's only altered files that are not.
Also, the files in the top directory are listed, but they're not actually being downloaded/synchronised regardless (and the up/down arrows previously present are not) for me at least.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Improvements in ca1609f.

@cyberduck
Copy link
Collaborator Author

shoestring commented

i just checked using the latest nightly Version 2.8b1 (3223) after it failed to work with the newer 'official' release.

Synchronise is still not mirroring modified files. New files up/download fine. But all files present both locally and remotely, while all now showing up, are now un-checked and greyed out, even if they are different size/have different timestamps (this is even recognised by cyberduck in the 'details' part). Ticking the box seems to have no effect.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Resolved in c9c9757.

@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.
Projects
None yet
Development

No branches or pull requests

2 participants