We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Lost files after enabling Selective Sync
What the **bleep**!?
I just lost tens of thousands of crucial log files because I happened to move a large archive folder into Dropbox, then decided not to sync the log folder.
Why the hell would...
Because that is exactly what you told it to do. And what you confirmed it to do when you are given the pop up prompt.
Edit: that said as long as you are quick and reverse that Selective Sync choice via the menu as Dropbox uses an internal cache you may find that the files are restored - even those none uploaded.
vadoff wrote:
It shouldn't even be designed in such a way that unsyncing something deletes it from the local computer
Yes, it should, when the entire purpose of the feature is to remove a folder from the local drive. That's the point of Selective Sync. It's not meant to allow you to store a folder in your local Dropbox folder that doesn't sync. It's meant to REMOVE folders from your local drive to save disk space while keeping those folders stored in your account online.
It clearly states that the folder will be removed; both in the documentation for the feature and in the confirmation that appears.
You said:
"It's not like it even went into the trash can, which would be annoying but at least acceptable. If it's going to be PERMANENTALLY DELETED, such a warning should be present and made absolutely clear."
The key thing (which I haven' seen any of the previous responses point out) is that the files have not been permanently deleted. If you go into the selective sync box and re-enable syncing for the folder (it will be available there), then it will re-appear on your local computer. It will take downloading of the many gigabytes of the files from the cloud, so do it on a fast network connection, but they have not been deleted if you just did what it seems from context.
Good luck, hope you get your files back!
That warning is nowhere near informative enough.
"Removed from this computer's Dropbox" could simply mean unsync'd. I've never seen any other program where such a destructive action that could potentially delete GB of files be worded in such language before.
It's not like it even went into the trash can, which would be annoying but at least acceptable. If it's going to be PERMANENTALLY DELETED, such a warning should be present and made absolutely clear.
This is such an obvious design flaw, the fact that it's present and you're defending it is simply mind boggling. It shouldn't even be designed in such a way that unsyncing something deletes it from the local computer, that's a behavior that I'm sure almost no user wants. And at the very least, there should be multiple options that the user could select in order to handle those unsync'd files: "leave it alone", "delete them", etc.
I thought Dropbox had some decent designers, come on this is design 101.
Rich
Super User II
Super User II
vadoff wrote:
It shouldn't even be designed in such a way that unsyncing something deletes it from the local computer
Yes, it should, when the entire purpose of the feature is to remove a folder from the local drive. That's the point of Selective Sync. It's not meant to allow you to store a folder in your local Dropbox folder that doesn't sync. It's meant to REMOVE folders from your local drive to save disk space while keeping those folders stored in your account online.
It clearly states that the folder will be removed; both in the documentation for the feature and in the confirmation that appears.
So I was expected to fully check the documentation of the feature before using it? Come on.
Once again, the wording of the window popup isn't clear enough AT ALL for the dire action it's about to perform.
You guys are useless, I'll just email some Dropbox designers or PMs directly.
No, it most certainly should not.
This is a total deviation form functionality, intended or otherwise, from previous releases - and is a sharp contrast to many other cloud sync tools we have ever used.
Example of old behaviour: Source folder that is shared across multiple devices. Each device needs a unique local config. Solution before last update? Uncheck the config file/folder. Now each computer has a local copy of their own config which does not overwrite all others, nor gets deleted by dropbox.
Since Update: All configs are destroyed. An outdated copy is possibly accessible through a convoluted web interface.
And that is why we cancelled all corporate and private accounts and are moving to Google Drive and GitLabs.
Dropbox have certainly dropped the ball on this one. Total deal breaker.I NEVER write on these type of forums but this is beyond a joke. I was working in sync with a project on my work computer and I didn't want to massive amount of cache files to transfer over (100+ GBs) so I unsynced that folder. Just like everyone else on here it deleted all of my local files. Literally a week of simulation and data processing gone without a decent warning. I have a choice of waiting days for it download or days to redo all the work. Honestly this is a massive design flaw, I don't care how you think people should interpret the feature.
FIX this bug/feature now. This is surely not how people expect to work. I don't see how I can even use Dropbox from now on, I'm afraid to do anything incase it simply wipes the entire project without warning.
Local files should always stay safe! Massive warning boxes should pop over if local files are going to be wiped. This has thrown a massive spanner in my job. I don't even know what to say.A link to a statement from RICH SuperUser that Dropbox never behave different delete files from the local drive.
https://www.dropboxforum.com/t5/Dropbox-files-folders/News-on-selective-folder-and-option-that-prevent-deleting-these/m-p/402535/highlight/true#M147467
The name should not be selective synch !
I also expected the folder to stay here locally and not be synched to the cloud.Really wrong on many levels.
Ok, it says that. But it is a huge change from previous behaviour. That should be announced clearly. I don't expect an old feature to change without notice.
In any case, it seems quite a silly change. The most important problem people have is that dropbox synching conflicts with projects of various programs (for example Rstudio). Now you introduced this stupid feature to have a file on the cloud and remove it from the hard drive. if I want to delete a file I can do it by myself and I if i want to keep it somewhere else I have lots of ways of doing it.
So, the problem is nopt having a pop up nortice but:
1) having completely changed a previous command without changing its name
2) ahve removed a useful feature for a dangerous one which doesn't seem to be useful at all.
I saw people asked for away to have filetypes ignored, like *.log, *.proj, ecc. Before it could be done manually with selective synching, now I need to disable synching alltogether.
I cannot access that window you speak of .. how do get it besides waiting for it to "appear" becasue it is not appearing.....
Rich,
The reasoning is arrogant and condescending. It does not help any of those present who are struggling with this problem to ride around on any documentation and proclaim it as a law like the holy Inquisition.
This behavior was newly added in 2018 and it's a design fail for a lot of reasons and the Dropbox company is be responible for this data loss behavior! In previous versions this behavior never happen.
I pay for my dropbox account, and I want decide what files are beeing on the dropbox space or what files are not. It doesn't matter if the files are synchronized directly with a device or not.
You should support people with an option that switching off selective synchronization does not automatically lead to the deletion of files on all devices.
1) Give legal reasons against this procedure.
2) Tell me the exact date and Dropbox version number, since when have you introduced this new procedure for deleting the data on the connected devices, which have to do directly with the deactivation of the synchronization of folders.
Dropbox will never admit to any fault, nor make any effort to rectify this situation. Their stock response is (and always will be) "it is supposed to break, we just didn't notice it wasn't breaking, so we went ahead and fixed it so that it breaks now". My team lost a lot time due to this crazy dogmatic thinking. Luckily, we had other backups (Backblaze). Back in October, we canceled all dropbox accounts and moved everything to GitLabs. Best move we ever made. Google Drive is also a good replacement, allowing selective sync like Dropbox used too. They offer more free space, and more space for the money if you pay for G Suit. Thier sync app uses less resources, and sync speeds are much better too. Unfortunately, Dropbox is just not worth the time anymore.
I do not talk to any unknow user
