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

(S)FTP: Uploading a new file with the same name replaces exiting file #2025

Open
jkaberg opened this issue Oct 26, 2016 · 4 comments
Open

(S)FTP: Uploading a new file with the same name replaces exiting file #2025

jkaberg opened this issue Oct 26, 2016 · 4 comments

Comments

@jkaberg
Copy link

jkaberg commented Oct 26, 2016

Per title, whenever I share a file to my sftp which has the same filename as an exiting file (on the sftp) it will replace the sftp one

Perhaps an option to append (or prepend?) chars/numbers to the filename?

This affects paste and file uploads AFAIK

@Jaex
Copy link
Member

Jaex commented Oct 26, 2016

One of the reason why I didn't add auto renaming to not replace file because then each upload needed to check is file exists which would slow down uploading process and not preferable.

@jkaberg
Copy link
Author

jkaberg commented Oct 26, 2016

@Jaex Thats totally understandable, but perhaps make it optional? And the onhover baloon could imply that an additional delay needs to be accounted for when using this option

I don't mind if it takes an additional 1-2s

@Jaex
Copy link
Member

Jaex commented Mar 23, 2017

There is also another reason that "early url copy" option won't work with it. Because this option copies url before upload start. But when file exists detected it will require new name so that early copied url will be invalid.

@tudormateescu
Copy link

I think this is a problem too, just now I've observed that. I think a solution would be great here - a random name or string attached to the uploaded filename for example...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants