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
Using sftp, when you upload to a Mac OS X directory ~/Users/joeblow/Public/Drop\ Box/, the user does not have permission to view somebody else's drop box. But every time you try to upload a file into a drop box, Cyberduck seems to want to always list the destination remote directory after uploading, so you always have to dismiss an error panel.
One solution would be a Don't tell me this error again checkbox in the panel that shows the permissions error. Then at least it would only tell you once per session. A better implementation might be a preference to just never report a directory listing permission error when trying to retrieve a listing from a closed folder you just dropped something on.
The text was updated successfully, but these errors were encountered:
Maybe related to this is the drag & drop handling. Cyberduck tries to list the FTP folder on rollover. When it's a write protected FTP folder it generates an error. When dragging a file to the FTP directory you sometimes roll over other directories in order to get the one you want to drop it into, generating this error; a bit annoying.
Using sftp, when you upload to a Mac OS X directory
~/Users/joeblow/Public/Drop\ Box/
, the user does not have permission to view somebody else's drop box. But every time you try to upload a file into a drop box, Cyberduck seems to want to always list the destination remote directory after uploading, so you always have to dismiss an error panel.One solution would be a Don't tell me this error again checkbox in the panel that shows the permissions error. Then at least it would only tell you once per session. A better implementation might be a preference to just never report a directory listing permission error when trying to retrieve a listing from a closed folder you just dropped something on.
The text was updated successfully, but these errors were encountered: