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 would like to voice my opinion on this bug. I apologize in advance if this is not the most appropriate forum.
This may be arguing semantics, but setting the bug type as an enhancement rather than a defect is wrong in my opinion. This is not a "new feature", but rather unexpected/unintended/unintuitive behavior in its current form. When a user selects "Toggle Log Drawer" and does an SFTP/SCP transfer, and nothing appears there, they think something is wrong - and it is. At the very least, there should be a log entry that pops up there saying that logging is not yet available for SFTP/SCP, otherwise the user is kept completely in the dark about it. They shouldn't need to know in advance that the logging is dependent on which protocol they use to do the transfer.
In my situation, I use Cyberduck almost exclusively with SFTP/SCP now, so this is a critical issue for me. In particular, whenever I use the "synchronize" option, I need to be able to see a transcript of what files were transferred, since it could cause problems if files were overwritten, deleted, etc. without my knowledge. To synchronize a whole directory hierarchy with absolutely no indication of what occurred is playing with fire. It has become such a big issue for me that I had to switch to FileZilla instead until this bug is addressed.
I have a lot of respect for Cyberduck's interface, but this is clearly a bug that should be resolved by now, after being open for two years. I am anxious to see it completed by the 4.0 release.