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

Unable to overwrite existing file #11220

Closed
cyberduck opened this issue Oct 29, 2020 · 2 comments
Closed

Unable to overwrite existing file #11220

cyberduck opened this issue Oct 29, 2020 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Oct 29, 2020

845ca6f created the issue

The misbehaviour manifests in one of the two scenarios:

  1. When changing file's location by dragging if the destination already contains a file with the identical name an error alert is raised.

  2. When uploading a file with a name identical to the existing one on Google Drive the file being uploaded is skipped (ignored) despite the fact that under the "Uploading" section of Cyberduck's settings the option to show the prompt is checked.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 5, 2020

@dkocher commented

I cannot reproduce this issue as the prompt is shown here. Unless you reload a file transfer then it depends on the additional setting Always overwrite when reloading.

@cyberduck cyberduck closed this Nov 5, 2020
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 7, 2020

845ca6f commented

I set to "Always overwrite" and it did the hob, however when I set to "Prompt" the next time I uploaded the same file and moved to the same folder there was no prompting. The option to "Always overwrite when reloading" was enabled since the beginning.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 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