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
change my dropbox folder name on my PC
I have my dropbox folder in the D drive of my computer. For some reason, the dropbox folder is not named "D:\Dropbox", but "D:\Dropbox (Elliotfan)" with my account name together. Does anybody know ho...
Hi Emilio,
I can only confirm what Rich already pointed out.
Dropbox for Business will allow you to access both your personal Dropbox and your work Dropbox from the same computer. To help signify which Dropbox folder is connected to which account, we've chosen to rename the business Dropbox to "Dropbox (business name)." Currently, there is not a way to change the name of this folder back to just "Dropbox".
By default, we place a hidden symlink from Dropbox to the new Dropbox (team name), so you may find that your applications can continue working by accessing this symlink.
However, if this does not work for you, and if you are comfortable creating symbolic links on your machine, there is a workaround that may help you. Please note that this workaround is not supported by our support team, so if you are unable to set up this environment, I'd recommend that instead of using this workaround, you move any files needed by your affected application out of your Dropbox folder instead.
If outside code sources don't cooperate with the space character or parenthesis character, the simplest workaround would be the following:
- pause Dropbox
- remove the hidden symlink at Dropbox
- Rename the "Dropbox (team name)" folder to Dropbox
- Place a symlink at "Dropbox (team name)" that points to "Dropbox"
- Resume syncingThis will allow Dropbox to continue accessing the content through the symlink, and it will allow any external code to use the "Dropbox" folder pathname that doesn't include the additional characters in the path.
I hope this helps!
Yeah, I can get around it, its just causing unnecessary complexity and issues with my setup. I have some node modules that are tripping over the space and I'm not about to monkey patch 3rd party dependencies to get around Dropbox's space when there are other options. For me its not the end of the world to work around, but I don't want it to be company policy to have to explain an undocumented and unsupported hack to everyone on my team every time they get a build error or filepath issue. I rely on my cloud service too much to have a symlink hack in the middle of it, even if only for my general piece of mind.
Been on Dropbox Pro for years and years ( along with my team that I also pay for ), and have had Dropbox personal since pretty much Day 1. There's been a few rough patches in the past, and I keep coming back because Dropbox is a great tool with excellent customer support. But yeah, going down my list of other cloud services... c'est la vie.
