You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
I keep getting selective sync conflicts by Dropbox?
I have a major issue with sync conflicts at the moment, which i'm trying to resolve. Although what I find happening is that files are being moved by drop box into my private folder.
I've tested...
Okay, I will try.
In using Selective Sync, (as an example) you selected Folder B and Folder D. Once you selected those folders in the Selective Sync Settings, Those folders will disappear off your Dropbox folder. It will be in the cloud only.
Let's say you had the same files that were in Folder B and D somewhere backed up (outside of Dropbox folder) and place them inside the Dropbox folder. It will create conflicted copies. That is because it's supposed to be 'off' your HD (off from your Dropbox folder)
Now, this is the way I understood from your Post. Its possible and not inconceivable that I may not have understood the situation.
But does this sound what happened?
This bug is awful.
1. Get tired of Dropbox relentlessly syncing scratch file folders, like the ones Visual Studio uses to store temp files in a Project's folder - you want the important Project files to be backed up continuously, but not the needless, frequently-modified temp files.
2. Remove those folders from Selective Sync.
3. Dropbox does the opposite of what you wanted - it keeps them in the cloud and deletes them, needlessly, from your machine - the exact opposite of what you were really asking, but whatever as long as it stops syncing useless folders.
4. It makes things much worse. A cascade of (Selective Sync Conflict) folders appear recursively on your machine, forever.
I'm really tired of getting prompted to pay more for Dropbox when they can't give us basic features like Ignore Folder. The feature request was on the Dropbox community and seen by Dropbox staff over 5 years ago. Embarrassing.
- Lusil
Dropbox Staff
This is still happening.
Steps:
- Create a folder, let's call it foo
- In foo, create a folder called "node_modules"
- Go to Dropbox client, Selective Sync settings, and uncheck node_modules
- Wait for sync
- Verify on Dropbox.com that "node_modules" exists and is empty. Verify on local machine that folder no longer exists and Dropbox is 100% up to date and done syncing.
- Create a folder called "node_modules".
Expected:
- Folder exists locally, but does not sync because of Selective Sync settings. Files in that folder also do not sync.
Observed:
- Dropbox forcibly renames folder to "node_modules (Selective Sync Conflict)" no matter how many times you try to name it "node_modules".
This behavior is completely blocking my flow. It is contrary to the way Dropbox has worked for years. It was always incredibly annoying to have to go through all these steps every time I make a new project to avoid needless syncing...but at least it worked. And now, suddenly, it doesn't.
Your suggestion to "rename the conflict folder" is vague. Rename the local folder? It must be "node_modules" and your software is preventing that. Rename the destination folder? Then Selective Sync won't know not to sync node_modules. Rename it to node_modules after the forced rename? Wish I could, but you, Dropbox, are preventing that.
If this isn't fixed, I'm done with Dropbox. It's been a nice decade, but you guys are obviously not interested in supporting your customers. It's one thing to not implement features like wildcard ignore that have been asked for for years, and another to break the one (terrible, but functional) workaround for your own application's shortcomings.
Also, new member, created 30 seconds ago? I signed up during the beta in 2008. I've made posts on the Dropbox forums that are almost old enough to get their own Dropbox accounts. Get your act together.
