We've recently begun using Dropbox as a collaboration tool within our company. We've encountered some quirky issues, and were hoping the community would share some Best Practices tips and tricks, do's and don'ts, etc!
Several of our developers have reported that occasionally they are unable to save a file that is opened from a DB folder, or have experienced crashing when working or publishing from a file that is in DB. Some of our viewers who are watching a course that is in the DB public folder have issues: video is slow or doesn't run at all, narration notes are missing. These people are all on quad-core computers, with decent internet connections.These issues don't occur when we use our server, but I would prefer to use DB with our developers so we always have access to current files that they are working on.
I have recently experienced a similar issue with Engage DB files that were ported into a Storyline DB file and the updates didn't take when the course was published. Very frustrating!
If you don't get what you need here, try searching the forums. There have been several Dropbox conversations in community. You may find something helpful in a previous post.
DropBox doesn't cache pages so it can cause issues for folks sharing published output files. We use Dropbox for sharing projects and haven't seen issues normally associated with network sharing.
Checking out DropBox's forums, I found some people reporting that DropBox locked their files which prevented them from saving. It seems sporadic but you could try doing a Save As... to see if that corrects the issue. I would also recommend you try turning off DropBox when you're working to see if that resolves the issue.
What version of DropBox are you using?
If you need a temporary place to test your content, check out our Tempshare site:
For the most part, we really like using Dropbox (version 1.4.7 is my current version), we just had a couple of team members who continually had issues. I have a feeling they were trying to work from files that were in DB. I've found that is not such a good idea. It's better to use DB as shared storage and file transfer space, moving the files to a local folder to complete work, and then Save As to DB. We've also stopped using the Public folder as a location to show published output since it was unrealiable. Now I know why- thanks David!
Good to know about tempshare. As always, great support!
6 Replies
Hi Diana,
Perhaps you could share a couple of the "quirky" issues to see if I've run into any of the same problems.
Cheers,
Several of our developers have reported that occasionally they are unable to save a file that is opened from a DB folder, or have experienced crashing when working or publishing from a file that is in DB. Some of our viewers who are watching a course that is in the DB public folder have issues: video is slow or doesn't run at all, narration notes are missing. These people are all on quad-core computers, with decent internet connections.These issues don't occur when we use our server, but I would prefer to use DB with our developers so we always have access to current files that they are working on.
I have recently experienced a similar issue with Engage DB files that were ported into a Storyline DB file and the updates didn't take when the course was published. Very frustrating!
Hi Diana,
If you don't get what you need here, try searching the forums. There have been several Dropbox conversations in community. You may find something helpful in a previous post.
Hi Diana,
DropBox doesn't cache pages so it can cause issues for folks sharing published output files. We use Dropbox for sharing projects and haven't seen issues normally associated with network sharing.
Checking out DropBox's forums, I found some people reporting that DropBox locked their files which prevented them from saving. It seems sporadic but you could try doing a Save As... to see if that corrects the issue. I would also recommend you try turning off DropBox when you're working to see if that resolves the issue.
What version of DropBox are you using?
If you need a temporary place to test your content, check out our Tempshare site:
http://tempshare.articulate.com/
Thanks all!
For the most part, we really like using Dropbox (version 1.4.7 is my current version), we just had a couple of team members who continually had issues. I have a feeling they were trying to work from files that were in DB. I've found that is not such a good idea. It's better to use DB as shared storage and file transfer space, moving the files to a local folder to complete work, and then Save As to DB. We've also stopped using the Public folder as a location to show published output since it was unrealiable. Now I know why- thanks David!
Good to know about tempshare. As always, great support!
This discussion is closed. You can start a new discussion or contact Articulate Support.