Skip to main content
Known Participant
November 28, 2017
Question

Captivate 2017 publishing a blank html page

  • November 28, 2017
  • 3 replies
  • 833 views

After publishing and viewing content, the html page is blank. However, I can view the swf file. This is the first time this has happened on my published Captivate 2017 project. Anyone else have this happen?

This topic has been closed for replies.

3 replies

Lilybiri
Legend
November 28, 2017

If you talk about publishing to HTML5 (not really clear from your question), this happens often to me as well when I want to watch the published file locally. I have to upload it to my domain or to a webserver.

Known Participant
November 28, 2017

It's a Google Chrome issues. My company updated and it blocks flash. I'm using Firefox and it's fine. Sorry I didn't state in my original question that I was publishing SWF. It's not a Captivate issue.

Lilybiri
Legend
November 28, 2017

Well, this is astonishing that you are still publishing to SWF. If had known that I would have asked about the used browser. Not only Chrome is not installing the Flash player plugin anymore by default.

RodWard
Community Expert
Community Expert
November 28, 2017

If you are using a Windows browser, try viewing the content in a different web browser such as Chrome.  If you then are able to view the content properly, the issue is most likely due to security restrictions and settings in place on your normal browser.

Try uploading the content to a web server and viewing from there.  If you can view the SWF content in the browser from the web server, but not locally, then the issue is most likely due to Flash Global Security being disabled when viewed locally.  Some newer browser updated versions are now making it increasingly difficult to view any Flash SWF content, requiring the end user to specifically enable the SWF content to play on a domain-by-domain basis.  It's just the browser vendors way of killing off Flash sooner than it was supposed to die.

Erik Lord
Inspiring
November 28, 2017

Not had this issue myself.

Save-as to a new version of the project

Publish to a different location/folder

Check the 'Force Re-Publish All The Slides" option (I believe it's still in the 2017 version)

Helps?