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!
Hi Sofia/All.
I came here from: https://www.dropboxforum.com/hc/en-us/community/posts/202867585-How-do-I-rename-the-root-folder-
Like Emilio D. I also use LaTeX, Mathematica and develop codes Matlab / C. Which means change path names is a terrible headache.
I decided to test the Team Account option for Dropbox during this week, so my coworker and I could share this Team folder and not the "old school" shared folder.
Worst idea!
Every program lost track of shortcuts... well not a big problem, it is just have to find them. But when I starter to check LaTeX reports and some codes paths I realize the huge headache.
"Dropbox" changed to "Dropbox (anything)", that meant some LaTeX data bases like .bib bibliography we share from a single folder and others .cls files could not be found by LaTeX just because of the !dammit! space, and then I realized the same would occur for codes.
Options OR change the location structure OR find a way to rename Dropbox back again. I knew I couldn't do it while it is synchronizing. I read the steps above for Business and then I did these:
1) Stop Dropbox Sync
2) Change the name back to "Dropbox"
3) Restart Sync - Receive message about the change of name and if I would do a new installation or use the old name and settings for "Dropbox (anything)" by renaming this path again. I chose a new installation.
4) Download Dropbox Installer from my account on dropbox.com
5) Reinstalled Dropbox on My PC.
After some - a lot of - time all files were re-synchronized.
I beg you for next upgrade, give us the option to choose the name of the new Dropbox, I saw no need to change the old Dropbox just because there is a new "Dropbox (Team)" folder. Don't change the name of folders without asking for it. And as I learned with codes and so on:
DO_NOT_USE_SPACES_OR_ACCENTS_ON_NAMES_FOR_CODE_DATA
If the new name was "Dropbox_Specification", I could simply rename paths as I need, but the space character just made it impossible.
I hope my words may help.
FHZ.
- I just chatted with the help desk about this and apparently NO ONE ever read this message. Because they would have fixed this over the past year.
