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
It appears that when you edit a file by hitting Edit in Cyberduck, then save a new copy of that file in the editor, the following happens:
Cyberduck detects a change to the file
Cyberduck uploads a copy of the file with a GUID attached to the end of the filename.
Cyberduck deletes the original file from the server.
Cyberduck renames the version with the GUID back to the original name by removing that GUID.
I had a situation today on an IIS 8 server where, due to a problem with SSL configuration on FTPS (FTP+SSL), file uploads did not work. That is not the issue; the issue is even though the file uploads did not work, Cyberduck still proceeds with the edit change process by deleting the file and then renaming--oops, there's no file to rename! End result is that if you edit a file and then save it, it got deleted off the server (!).
Attached is a screenshot of the log drawer where you can see that Cyberduck got a 550 error. Cyberduck should have stopped IMMEDIATELY upon seeing the 550 error and warn the user! Unfortunately, Cyberduck did not stop, and it did not report anything to the user. If the log drawer was not opened, the only way I know something happened is that the file went missing.
It appears that when you edit a file by hitting Edit in Cyberduck, then save a new copy of that file in the editor, the following happens:
I had a situation today on an IIS 8 server where, due to a problem with SSL configuration on FTPS (FTP+SSL), file uploads did not work. That is not the issue; the issue is even though the file uploads did not work, Cyberduck still proceeds with the edit change process by deleting the file and then renaming--oops, there's no file to rename! End result is that if you edit a file and then save it, it got deleted off the server (!).
Attached is a screenshot of the log drawer where you can see that Cyberduck got a 550 error. Cyberduck should have stopped IMMEDIATELY upon seeing the 550 error and warn the user! Unfortunately, Cyberduck did not stop, and it did not report anything to the user. If the log drawer was not opened, the only way I know something happened is that the file went missing.
Attachments
error.png
(22.1 KiB)The text was updated successfully, but these errors were encountered: