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
Many team members can't see on their desktop app the files I've moved, or they get an error.
Hello. I use the web version of dropbox (www.dropbox.com) to organize files. Many of my team members prefer to use the DESKTOP version of drop box and open files through File Explorer. Many of the files that I've "moved" or reorganized via the web version cannot be seen by my colleagues who use the desktop version. Can anyone shed some light into how we fix this? The error message these users get indicates the file isn't found or can't be opened.
- Nancy, thank you for the post. I think we've figured this out. We determined it was actually an ADOBE setting that was causing the problem. We've UNCHECKED the 'Enable Protected Mode at Startup' and it seemed to work. This is a known ADOBE issue as I understand.
We'll see if this continues to work!
- Nancy, thank you for the post. I think we've figured this out. We determined it was actually an ADOBE setting that was causing the problem. We've UNCHECKED the 'Enable Protected Mode at Startup' and it seemed to work. This is a known ADOBE issue as I understand.
- Nancy
Dropbox Staff
Hey Tami! Thanks for posting on our Community today!
Can your team members see your updates on www.dropbox.com? Are they getting any errors there?
Do all of your members have this issue or only specific users? Do you have a screenshot of the error(s) they receive, so that you can post it here?
Let me know once you have more info.
- Nancy, thank you for the post. I think we've figured this out. We determined it was actually an ADOBE setting that was causing the problem. We've UNCHECKED the 'Enable Protected Mode at Startup' and it seemed to work. This is a known ADOBE issue as I understand.
We'll see if this continues to work!
- Nancy, thank you for the post. I think we've figured this out. We determined it was actually an ADOBE setting that was causing the problem. We've UNCHECKED the 'Enable Protected Mode at Startup' and it seemed to work. This is a known ADOBE issue as I understand.
