-
-
Notifications
You must be signed in to change notification settings - Fork 296
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
Copy/Duplication of File breaks 'link' to File Editor #5524
Comments
I cannot replicate any of the two issues. Can you try to reproduce the problem and, again, let me know the exact steps to follow. |
I want to point out that I first ran into this problem months ago, or even years ago. I'll start with more explicit repro steps for the 'duplicate file' version of the issue.
I can reproduce this on different machines, connected to different servers. I haven't tried it with different text editors. |
Thanks for the details. I will try once more to reproduce. Reopening this issue. |
Replying to [comment:3 logicbus]:
Edited files uploaded never appear in the Transfers window but are uploaded using the browser connection. |
Replying to [comment:3 logicbus]: Can you check what the output in the log drawer of the browser window shows after hitting Save in the editor. |
Replying to [comment:6 dkocher]:
|
I can replicate the issue now.
|
Cool! Have you tried reproducing it by dragging a file from a Cyberduck browser window to a Finder window, rather than duplicating a file in a browser window? I can list out steps for that, if needed. |
A new snapshot build will be available in a few minutes. Please reopen this issue if you can still reproduce the second issue. |
When I tell Cyberduck to open a file (from an FTP server) in my text editor (TextWrangler) I can edit and save the file normally. However, if I
or
Curiously, after copying the file to my local machine, I get a Growl notification that the file has been uploaded (even though it hasn't). After duplicating the file, I got no Growl notification. (This makes me worry that these are two separate bugs, but they've got to be related ... don't they?)
The text was updated successfully, but these errors were encountered: