Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
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 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.
Rich
Super User II
Super User II
kenjura wrote:
Expected:
- Folder exists locally, but does not sync because of Selective Sync settings. Files in that folder also do not sync.
Dropbox no longer operates that way. The functionality was changed as that was not an officially supported function of Selective Sync.
Dropbox now has a method in beta that allows you to set Dropbox to ignore files and folders. The new method is not yet available to all users.
