Add option to Replace folders on upload (instead of the default Merge behavior)

[joelstein]

Reference previous topics on the matter:

• http://www.yummysoftware.com/forum/index.php/topic,753.0.html
• http://www.yummysoftware.com/forum/index.php/topic,401.0.html

Okay, I'm not a big fan of directory merging at all.  I think it's counter-intuitive.  If I upload a file, I don't expect it to merge the changes, but to replace the file.  If I upload a folder, I expect it to replace the folder.  That is, completely, not merging or leaving old files online.

For most new users, that will be what their expected behavior is.  If a user wants to merge, they should use the already available sync command (merging is practically synonymous with syncing).  Right now, if I want to upload a new version of a folder and it's contents, I have to sync.  In my opinion, that's backwards.  Merge means sync, upload means replace.

It's caused me many headaches since I switched to YummyFTP.  For instance, I do Drupal website development.  When a new Drupal module is released, it would be so fast to drag the module folder on the YummyFTP dock icon and have it uploaded, replacing the original contents.  As it is now (and this took me many frustrating experiences to figure out), it merges the files, leaving old, unnecessary and often troublesome files on the server, which sometimes causes the module to break (and the whole website, in certain circumstances).

While I respect the fact that others may not agree with me on the default behavior, I think at the very least there needs to be an option to choose whether an uploaded folder is replaced or merged.  I would prefer an preference setting, so I don't have to be asked every time.  Though, on some applications, I've seen the prompt appear the first time you upload a folder, giving you the ability to choose "Replace" or "Merge", and an additional checkbox that says, "don't ask me this next time."

Is there any chance that this feature can be added?

[JD]

All FTP clients have historically used the merge method because it is non-destructive. With a folder Replace instead of Merge, the target folder and all its contents must be completely deleted before its replacement can be transferred. That would make me nervous, to be honest.

Only recent FTP clients such as Transmit have offered the Replace option because it is (debateably) more 'Mac-like', but it has caused headaches because of the very issue I described above.

For what it's worth, files cannot be merged, only folders. I don't know where the file merge notion is coming from. That never happens for files. 

In any case, I could of course add such a capability if there is sufficient demand for it (please post your votes!) but Merge would still be the default behavior because that is the behavior that seasoned users of FTP would expect.

[joelstein]

Yes, it would be too late to make it the default behavior.  Having a preference setting where I could switch that behavior from Merge to Replace for folders would be immensely helpful to me, and hopefully to others.  Thanks!

[geerlingguy]

Only recent FTP clients such as Transmit have offered the Replace option because it is (debateably) more 'Mac-like', but it has caused headaches because of the very issue I described above.

In any case, I could of course add such a capability if there is sufficient demand for it (please post your votes!) but Merge would still be the default behavior because that is the behavior that seasoned users of FTP would expect.

I second joelstein's plea for the option to replace rather than merge folder contents. As a user who mostly worked with Transmit and Coda before coming over to Yummy, I was very confused when I found that the directory was not replaced when I dragged an entire directory on top of it.

I think having the setting would be acceptable; there's a setting for just about every other option under the sun (which makes Yummy totally rock, btw).

[JD]

That's a pretty nice vote! Adds great weight to the feature request...

[paulc]

Ad me to the "choice" group, better too have a merge or replace choice.

[ljmac]

Once again, the ancient MacSFTP does this is in the most logical and intuitive way. It replaces files first, then deletes any files not in the replacement directory afterwards. This is relatively safe, and also faster than deleting everything beforehand.

BTW, how is 1.8.3 coming along JD? I'm still annoyed by the multiple file permissions change behaviour. 

[JD]

Once again, the ancient MacSFTP does this is in the most logical and intuitive way. It replaces files first, then deletes any files not in the replacement directory afterwards. This is relatively safe, and also faster than deleting everything beforehand.

BTW, how is 1.8.3 coming along JD? I'm still annoyed by the multiple file permissions change behaviour. 

Hey there

Thanks for the suggestion! That's a great approach.

I'm sorry for the delay on 1.8.3. Behind the scenes I've had some personal stuff happening, but I'm getting back on track now.

I have not forgotten your requests, don't worry

[ljmac]

Hi JD. Sorry to hear you've been having some personal issues (it happens to all of us sometimes), but I'm glad to hear you're back on track now.