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

Transfers only work to/from C: Drive #5306

Closed
cyberduck opened this issue Oct 12, 2010 · 1 comment
Closed

Transfers only work to/from C: Drive #5306

cyberduck opened this issue Oct 12, 2010 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Oct 12, 2010

1bcec21 created the issue

Cyberduck seems to be rewriting local paths to always be rooted from the C: drive, even if the real source is another drive or UNC path. Local and Network paths are affected. This definitely affects FTP and SFTP, I'm guessing it affects all protocols.

Examples:

  • ALL uploads, initiated via Keyboard (Alt+Up), Context Menu, File Menu, or Drag & Drop fail on all non-C: drive local paths. All paths have their local drive (D:, E:) or UNC server (\Server) rewritten to C:. Of course, since the file isn't actually there, the transfer fails.

  • Drag & Drop Downloads to paths not on C: drive have also have their leading identifier (e.g. D: or \Server) rewritten to C:. Transfers succeed, but the local path is rerooted to the C: drive. If a file was to be downloaded to D:\Path\To\File.zip, then the file is downloaded to C:\Path\To\File.zip. The \Path\To directories are created on C: if they do not exist. This happens for all non-C: local drives, mapped network drives, and UNC paths.

  • The "Download To..." command works correctly.

  • If the default download folder specified in Preferences -> Transfers -> General -> Downloads -> Download Folder is not on the C: drive, then the "Download" command fails in a similar manner as Uploads and D&D Downloads.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Oct 13, 2010

@ylangisc commented

In a8caa4f. Thanks for reporting this issue!

@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

1 participant