About Здравко

Hi @JAS37, Might be more easy, as an workaround, the content get be synced, not the container. ... View more

Hi @freeka, As you have described situation, share the folder and after that change the ownership would be the fastest way. Hope this helps. ... View more

Getting back earlier version is platform depending way. Dropbox daemon autoupdates whenever possible. Do your system provides some way freeze it? If so, this is the way. 😉 ... View more

Hi @harry t.4, From info above seems user 'Dadjohn' have "died". But still owns your Dropbox directory. You can get back the owning using: sudo chown "$USER" "/Users/Dadjohn" sudo chown -R "$USER" "/Users/Dadjohn/Dropbox" Will be asked for your password (sudo). Hope this helps.  ... View more

Hi @avingochea, As far as I know, when there are some files and/or folders with same name (case insensitive) - name conflict is guaranteed. This is not for last version only! If you want to ignore server version of particular folder (as you have described), just remove the server version, using web interface, before change anything in "Selective Sync". Hope this helps. ... View more

Hi @lucioh, As far as I can see, you are using beta build! Try stable release. Make sure "Early releases" in General Settings is turned off. Then using offline installer try latest stable release (the current one). Hope this helps. ... View more

Strange... Such thing shouldn't happens. Would be normal if Dropbox folder sits on client side mounted network drive (such thing could happen even on server machine - in same time server and network client). So, changes in the disk FS don't always propagate correctly to all client mounts (including on server machine) resulting in an application which rely to detect such changes (like Dropbox) can't work properly. In this context, are you sure that you placed the Dropbox directory on real ("raw") disk space? You can make a simple test to see, if your machine is configured properly. Open a simple text editor on your server, write something inside (doesn't matter what) and save the file inside Dropbox directory (keep the editor open). File should be visible on the other workplaces. On some other machine (network client, workplace) open the same file and make some change inside (doesn't matter what) and save. Now, is the last change detected on server side - on both/some of the text editor (still open there) and Dropbox application? (Present day almost all text editors are able to detect concurrent change, but not all. Select a suitable!) If text editor, running on server, successfuly automaticaly detect file change (and signal about somehow without any user intervention) and Dropbox application can't, then you can report a bug in the particular build. If the text editor can't detect change, check more carefully your settings. Hope this gives some direction. ... View more

Oh.. Seems link was corrupt. Try again. 😉 ... View more