Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
On Mac, aliases in Dropbox to folders within Dropbox no longer work across devices
I'm having the same problem as what the user Robio describes here:
https://www.dropboxforum.com/t5/Files-folders/Mac-aliases-within-Dropbox-used-to-work-on-all-shared-devices/m-p/370300
That disc...
I imagine everyone is aware of this, but I still had this thread bookmarked, so I just popped in to say this issue appears to be fixed. I don't recall when it was fixed, but I'm running Dropbox 97.4.467 and aliases are working across devices within shared Dropbox folders.
Now if we can just get them to fix the problem of locked folders/files being not staying locked...
Hi Folks
I too have exactly the same proble of aliases made between folders in DropBox used to work on MacOSX (for many years) and just recently stopped working. This has to be a generic issue and not specific to any particular user/files, so if there is a solutiuon, it would help teh whole community. Mnay thanks
David
Hi AgardD,
There could be 2 cases for aliases related issues. So generalization isn't good way - the two groups are very different!
The first case is Dropbox limitation related - fact that anything after aliases can't be "live" sync anymore (since some time). If that's your case, you should reorganize files/directories structure, so no more aliases from inside Dropbox directory, pointing outside this dir.
Second case is about aliases residing inside Dropbox directory and pointing within same dir borders. If the aliases are relative, you should not have any troubles. If they aren't, the picture gets more complicated. Such aliases will work only when Dropbox directory is placed on the same place, on all machines in sync literaly (i.e. everything in the path before "Dropbox" is same)!!! In all other cases an aliases created on one machine will (most probably) fail on another machine.
Let say there are 2 machines and on the first, user name is "UserK" - i.e. Dropbox will sit by default on "/Users/UserK/Dropbox" (for example) and on the second, machine user name is "UserL" - i.e. Dropbox will sit by default on "/Users/UserL/Dropbox". Let say in your account you have a directory and a file inside like "SomeDir/example.txt" and you want an alias to example.txt in the account root. One alias variant is:
example.txt -> SomeDir/example.txt
The above will work in all cases - doesn't matter where is created and where used. That's relative alias. Another alias variant is (created on the first machine for example):
example.txt -> /Users/UserK/Dropbox/SomeDir/example.txt
The above will work only on the first machine, but not on second! That's absolute alias. On the second machine actual absolute file position is "/Users/UserL/Dropbox/SomeDir/example.txt", but the alias don't point there. That's where the problem comes from. This issue isn't Dropbox application related, but the way alias gots created (actually the type).
AgardD, You can decide where your problem falls to and gets appropriate actions on. :wink:
Hope this casts some extra light.
