You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to use Synchronize to download all files in a certain server folder to a folder on my local computer. I set it to Download. It seemed to run the synchronization, but unexpectedly quickly. After it was done, all the files in the structure were on the local computer, but every file was 0bytes. When I looked at the server, the files there had been emptied as well! A huge amount of important files were emptied of all of their information for no apparent reason. This is a terrible bug, and I'm not sure why anyone would be using an application that could make such an error.
The text was updated successfully, but these errors were encountered:
-I am using OS X 10.9.5. Cyberduck version 4.7.2.
-I connect to a WebDAV server, choose the "Syncronize" option and choose "Download".
-What happens is: every file downloaded has 0 bytes, but also has with it a resource fork that takes 200Kb. I'm not sure about what's in the resource fork; it seems to be binary data (the icon, perhaps?) Also, every file downloaded has the Cyberduck icon, instead of the one corresponding to its type (HTML, TXT, etc.).
BTW, I have also lost data due to this: a few days ago I used Cyberduck for the first time and set it to "Mirror": I don't know how, but it overwrote all the files in the server and set them to 0 bytes. Since then, I've been making tests only with the "Download" option.
I tried to use Synchronize to download all files in a certain server folder to a folder on my local computer. I set it to Download. It seemed to run the synchronization, but unexpectedly quickly. After it was done, all the files in the structure were on the local computer, but every file was 0bytes. When I looked at the server, the files there had been emptied as well! A huge amount of important files were emptied of all of their information for no apparent reason. This is a terrible bug, and I'm not sure why anyone would be using an application that could make such an error.
The text was updated successfully, but these errors were encountered: