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
Comments
Thanks for the issue report. Please attach the file |
Milestone renamed |
Ticket retargeted after milestone closed |
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. |
Ticket retargeted after milestone closed |
You might be interested by #10191, which describes a related issue:
|
I cannot reproduce this any longer. |
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:
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.
The text was updated successfully, but these errors were encountered: