Skip to main content
A
adame16166214
Participant
February 24, 2022
Answered

blank screen after publishing

  • February 24, 2022
  • 1 reply
  • 1514 views

Hello all,

 

I have sent published Captivate 2019 presentations to a client who reports that opening the index.html file brings up a blank screen in their browser.

I am able to open it on my end (through Chrome) and have it work correctly.

Are there browser restrictions when trying to view the html file? I believe the client is using Microsoft Edge/Internet Explorer.

If this is the reason, has anyone found a work-around if the client is unable/unwilling to download Chrome? 

If there is any other likely cause of this, I would appreciate any help. Many thanks.

    This topic has been closed for replies.
    Correct answer RodWard

    If the client has an LMS then configuring the output for SCORM and sending them that ZIP archive to upload to the LMS should work.  The LMS is also a web server and it will first unpack the SCORM ZIP so that file relationships work properly.  Using an LMS would seem to be your best option.

     

    Another suggestion:  IF the client does not want to use their own LMS for this testing, then get a free SCORM Cloud account and upload your SCORM packages there to test.  Invite your client's approvers to view the content on SCORM Cloud so that they can see how it should also work on their own LMS.

     

    SharePoint won't work for this. It's designed to work like a File Server, not an HTTP web server.

     

    Additionally, you cannot just send someone a ZIP archive of Captivate content and hope this will work for them.  When they dive inside to find the index.html file and try to run that to view everything working, the relationships between files are broken due to the way ZIP files compress things.  This results in the content not working for them.  Even if they decompress/extract the content first, in many cases it still will not work because certain things in Captivate HTML5 will not work without a web server or LMS.

    1 reply

    RodWard
    Community Expert
    RodWardCommunity Expert
    Community Expert
    February 24, 2022

    Captivate's HTML5 content is designed to be viewed from a web server, not locally from the user's hard drive.  It should be compatible with either Chrome, Edge or IE11, but not earlier IE versions.

     

    The best test for your client is to upload the entire published output to a web server and send him the link to the index.html file there.  My bet is that then he would be able to view the content on his browser of choice.  If you are using PReview as HTML in Captivate to see the same content, you are really using a localhost web server to view it. 

    A
    adame16166214Author
    Participant
    February 24, 2022

    Hi Rod, 

     

    Thank you for your help! I'm afraid I'm unsure of what defines a "web server" in this context (my apologies). Currently, my only option for sending/transferring materials is through SharePoint, and I don't believe they can open something directly out of a zip file from there (again, my apologies if this doesn't sound correct - I've only worked minimally with SharePoint). They do have an LMS that they could theoretically upload the files to, but this is meant to be the review phase, not final product. I was hoping to avoid the hassle of including the LMS in the process until absolutely necessary.

    RodWard
    Community Expert
    RodWardCommunity Expert
    Community Expert
    February 26, 2022

    Okay, thank you very much for your help!

     

    I had assumed that sending the ZIP file and opening the index.html would work since I can do it locally on my own computer after publishing it. Shows that I have much more to learn about the inner mechanics. 

     

    Thank you very much for your help!


    When you publish locally from Captivate and accept the option to view the output, pay attention to the browser address bar.  You will likely see that this is allowing you to view the published HTML5 in a temporary localhost server.  That's why it works for you.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices