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
Dropbox is creating duplicate files as opposed to GoodSync
Hi. I have been using GoodSync for a few years. I have 3 licenses and use it to sync between 3 desktops and 1 laptop.
Lots of the data is not suitable for Dropbox (Essentials) storage and s...
Hello Nicholas M.5,
> Is it right that when Dropbox sees a conflict, it creates a duplicate like filename(2)
When the Dropbox desktop app creates a conflict file, you will always see the word “conflict” in the filename. The “(2)” you see is most likely due to “autorename”, which is a feature of Dropbox used when a file with the same name as an existing file in a folder is uploaded via the Dropbox website. To experience this, go to the Dropbox website, upload a file to a folder and then try to upload a file with the same name to the same folder. The “(2)” will be appended.
The autorename feature is also available with the Dropbox API, which GoodSync uses.
To sum up, if it’s not you or another user uploading a file via the Dropbox website with the same name as an existing file, then this can be attributed to GoodSync. The conflict files created by the Dropbox desktop application always have the word “conflict” in the filename and the name of the computer on which the conflict occurred.
Hope this helps.
Andrew (DBoxTips)
Now our whole Practice Documents folder (1000s of docs) has a "conflicted copy". And dropbox has no conflict resolution???
How does it make the conflict determination? Is it timestamp or the mere presence of two files of the same name?
How could a whole folder end up conflicted? Folders aren't opened in themselves.
I'm not interested in dropping Goodsync in favor of DP Paper. Some change in your software has made a complete mess of our entire practice documents, that had been seamless for 20 years.
So now I see why the FileName(1) problem came about.
Dropbox lacks an overwrite warning. Usually users are copying indentically named files to overwrite. Instead of notifying the user (asking), DB takes the liberty of creating a second file while the user has no idea what just happened unless they browse the folder and see.
I've got workarounds for all of this now. The last thing I am really lost on is how to track the different folders that are created for a shared user. I shared a folder named CollectIt and now he's on CollectIt(3). I don't see those folders in Windows explorer or the Dropbox webpage.
Feels like I have no control over what's going on.
