-
-
Notifications
You must be signed in to change notification settings - Fork 296
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 setting attributes for uploaded files with temporary filename option enabled #9819
Comments
What protocol do you use to connect to the server? |
Plain FTP. |
Please post the transcript from the log drawer of the Transfers window. Choose ⌘-L on Mac. |
Here you go. Would prefer if file wasn't made public. |
Looks like the transcript from the browser window. Can you double check to open the transcript from the Transfers window prior restarting a transfer. |
That was blank, so I Cmd+L and sent one I saw. Here is one from blank Transfers window after uploading file. |
Thanks for the transcript where we can see the source of the error.
|
If you mean the error is because no file exists, that's not true. See previous screenshots of file in Finder and when transferred to server. The files are being found and replaced, problem is the modified date on the server isn't being kept and changed to today's date. I think the problem is when files are replaced, Cyberduck thinks file is being modified, it's not. The data in the file hasn't changed, so file shouldn't be marked as modified regardless of whether it's being uploaded or downloaded (unless you tick off the preferences to keep timestamps). |
As a workaround, uncheck the option Preferences → Transfers → Uploads → Upload with temporary filename. |
Version 5.3.3 (23221)
Regardless of how Timestamps preferences are selected, when I place file on server, the modified date always changes to Today. This is not helpful. For example, if I replace a more recently modified file on the server with an older file, I want to see its modified date, and not today's because the file on the server hasn't been modified, just replaced. This used to work "as expected."
Attachments
Screen Shot 2017-01-21 at 12.35.05.png
(56.5 KiB)Screen Shot 2017-01-23 at 08.32.57.png
(208.1 KiB)log.rtf
(9.6 KiB)The text was updated successfully, but these errors were encountered: