When I save a Captivate (Version 9) File as HTML5, so many files are created compared to saving as SWF. Is there a work around for this, or are we stuck with uploading a plethora of files when publishing to a regular server or an LMS?
When you upload a SCORM to an LMS it's always just a single zip file, regardless of whether the contents are HTML5 or SWF.
If you are uploading to a web server, then you may also find that the server will allow you to upload a zipped archive that gets unzipped on the web server itself. If not, then YES you need to upload all files separately. But most good FTP apps do this easily. What are you currently using?
Thanks much Rod ... I don't typically use FTP. When I want to post files on one of our organization's web server, I transfer them first to my "H: drive," then an IT person puts them on the server. This process gets a little involved when I want to post a project where I developed the TOC (to shorten load time) by creating & publishing separate Captivate files which were linked by relative addressing.
Your workflow has some major potential fail points. You might be better off getting your IT person to use the method I talked about above where you send them a zip file and they unzip it on the server to overwrite any older version files. You need to make sure that he's not only uploading some of the files and not all of them.
What do you use for uploading? I use Fzilla, and that makes it very easy to upload all files in an unzipped published HTML5 folder in one click. Why would you need to upload each file separatelY?
Thanks much Lilybiri ... I don't typically use FTP. When I want to post files on one of our organization's web server, I transfer them first to my "H: drive," then an IT person puts them on the server. This process gets a little involved when I want to post a project where I developed the TOC (to shorten load time) by creating & publishing separate Captivate files which were linked by relative addressing
6
Replies
AdChoices