Backing up Articulate files published to WEB

Sep 26, 2016

Hi,

I have users creating video training using articulate.  I've read another discussion where it was advised not to store the published content to a file share as flash and articulate doesn't like this.  It was working up until last Friday so I'm not sure what happened but the video never starts and all we see is a circle of dots in the middle.  It only works locally stored even if I copy the locally stored content to file network share.  As a standard we always tell our users to back up their local files to the network shares where they can be restored if lost.  It seems that the community says not to do this as it changes the outputs when copied on to file share.  If they save it local then why couldn't they copy those files to a file share where someone else picks it up and copies it their local drive?  This is how we share files to web admins but it seems the designers will need to be able to upload directly to webserver which is out of process for us as approvals are needed.  How does articulate recommend backing up the videos outside of their local hdd?  I've tried publishing via CD and web then copying those to network, then coping those down to another computer and it no longer works but the original files on original computer works.  Web admins can't explain this and I'm at a lost.  I will try the email function which says it will zip it...hopefully that works and I can back that up on file server.  Any ideas what's causing this issue?

5 Replies
Crystal Horn

Hello, William.  Just to understand your workflow:  It sounds like your developers are creating and publishing their presentations on their local hard drives.  Are they publishing for the web format?  And once it is published, is it ever being loaded into a web server?  Or are those published output folders being copied to a network, and then copied to another hard drive for viewing?

The best way to view your published output would be to load it into the environment for which it was published (in your case, onto a web server) and then view it in that location.  Launching content locally, from the published output folder on your hard drive, can cause your content not to function properly.

Backing up your published output to another drive or network is ok, but we don't recommend trying to view it from the network location, or by copying it down onto another computer's hard drive.

The discussion that Michael shared deals with a problem loading the content locally from the published output folder on the hard drive, specifically if Chrome with Flash Player 23 is being used to load the content.

Let me know if my understanding is accurate!

William Phillips

Thanks for the reply Crystal.  That's exactly what I'm doing.  The developer is creating it and publishing via web option.  She then goes to local documents where the project is stored and runs the story.html.  It runs fine there.  Now she wanted to let others see what she has done and placed in on network share drive.  Manager goes and copies it down locally and tries to execute the story.html and nothing happens.  I guess I'm assuming this is supposed to work but sounds like it shouldn't.  At that point I should just take those files and place them on web server.  The manager kind of wanted to see what the video looks like before we put on web somehow which I think the solution for that is to just make publish via CD and use the portable launch_story app that comes with it to run it for review.  Could I take that same CD version and send it up to web server and point to the same story.html file that exists there and work?

Also had another issue....when using the email option outlook says it sent but I never get it...don't see it anywhere...junk nor clutter...any ideas there?

Ashley Terwilliger-Pollard

Hi William, 

It may work, but it doesn't always and especially with browsers moving to disable Flash local playback you'll run into more issues. You could publish for CD and then use that for testing, but you'd want to republish for Web to place up on the webserver. Instead of publishing twice what about adding it to a temporary testing site instead? There are a few options linked here. 

As far as the email, it may be too large a file to have gone through - but it's really dependent on the email server and set up. You see it in your sent folder, but not in any inboxes for another account? It sounds like it's stuck somewhere in the ether than. 

This discussion is closed. You can start a new discussion or contact Articulate Support.