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

Uploads not triggered for filename with quotes #9792

Closed
cyberduck opened this issue Dec 22, 2016 · 8 comments
Closed

Uploads not triggered for filename with quotes #9792

cyberduck opened this issue Dec 22, 2016 · 8 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Dec 22, 2016

919af4b created the issue

When I drag & drop a file from windows explorer onto the Cyberduck window it doesn't start an upload or show any message. It shows the cursor and window highlight when I drag the file over and just before I release, i.e. it looks normal, it just never opens the Transfer window or starts a transfer. Cyberduck is open to an S3 bucket to which I have full control. This used to work fine in the past. Are there any log files I can check to understand what's going wrong? The Log Drawer doesn't show any output when I perform this action.

It also wasn't working for me in this scenario:

  • shift-right-click on file in windows explorer > Copy as Path
  • click the Upload toolbar button
  • paste full path & filename into the Choose box and click Choose

The Choose dialog would close but no action would be performed. If instead I do the same steps BUT remove the leading and trailing double-quotes from the file path then it works fine. Perhaps when you drag-and-drop a file from Explorer it wraps the path name with quotes, and this is why it doesn't work with drag-and-drop?

I have version 5.2.3 (21496) but it's not available in the Version dropdown

NB: this isn't a new problem in 5.2.3; I upgraded to 5.2.3 because I had this problem with 5.1.0.20872 and I was hoping it was fixed in latest version. I'm pretty sure (but not 100%) that this wasn't a problem in my earlier version which was 5.0.3.20504.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 10, 2017

@dkocher commented

Thanks for the issue report. Please attach the file cyberduck.log in the application support directory.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 11, 2017

@dkocher commented

Milestone renamed

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 11, 2017

@dkocher commented

Ticket retargeted after milestone closed

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 18, 2017

919af4b commented

I'm now using 5.3.2

Log file is empty.

I emptied the file before relaunching CyberDuck, repeated the two types of uploads (drag & drop and right-click > upload including quotes in path) and nothing in the log file at all. I then tried the upload using right-click > upload and not wrapping the filename in quotes and the upload worked but again there's nothing in the log file.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 5, 2017

@dkocher commented

Ticket retargeted after milestone closed

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 13, 2018

11bfe86 commented

You might be interested by #10191, which describes a related issue:

  • on Google Drive
  • with non-empty folders
  • whose name contains a single quote

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 4, 2018

@dkocher commented

#10191 closed as duplicate.

Loading

@cyberduck cyberduck closed this Jun 4, 2019
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 4, 2019

@dkocher commented

I cannot reproduce this any longer.

Loading

@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
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants