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

Failure moving file if destination exists #7497

Closed
cyberduck opened this issue Oct 23, 2013 · 6 comments
Closed

Failure moving file if destination exists #7497

cyberduck opened this issue Oct 23, 2013 · 6 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Oct 23, 2013

a4c96ab created the issue

When I'm editing files directly on a particular ftp server in my external editor 'Sublime Text 2', when I hit save it creates a new file on the server. In the attached example it's a style.css file, but it also happens with other files .html, .php and so on - but only on this FTP server. If i try any other FTP in my bookmarks it works.

The problem was not there before upgrading to 4.4.

This it was it looks like in the log:

226 Transfer complete.
TYPE I
200 Type set to I.
PASV
227 Entering Passive Mode (81,95,241,205,228,40).
STOR /***/css/style.css-d1f1db4c-81a5-4bea-8e64-2c2a4a2fab07
125 Data connection already open; Transfer starting.
226 Transfer complete.
RNFR /***/css/style.css-d1f1db4c-81a5-4bea-8e64-2c2a4a2fab07
350 Requested file action pending further information.
RNTO /**/css/style.css
550 Cannot create a file when that file already exists.

Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 23, 2013

@dkocher commented

Added new hidden property editor.upload.temporary to disable the use of temporary name on upload when uploading changes from the editor on save.

defaults write ch.sudo.cyberduck editor.upload.temporary false

In a7640d0.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 24, 2013

a4c96ab commented

Just curious was this fixed in the newest beta release? Because I still get the error when running Version 4.4 (13566)

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 24, 2013

@dkocher commented

Replying to [comment:3 assentorp]:

Just curious was this fixed in the newest beta release? Because I still get the error when running Version 4.4 (13566)

No, we have not yet included a workaround other than the property above to disable temporary rename.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 24, 2013

@dkocher commented

This is a specific failure with IIS described in KB 309634.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 24, 2013

@dkocher commented

Replying to [comment:5 dkocher]:

This is a specific failure with IIS described in KB 309634.

This issue occurs if the AllowReplaceOnRename metabase property is not set to 1.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 24, 2013

@dkocher commented

Workaround in c0ece7f. Delete target file prior rename if it exists already for FTP.

Loading

@cyberduck cyberduck closed this Oct 24, 2013
@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