If you know of any helpful fixes or useful suggestions, users experiencing the issue discussed in this article would appreciate your support. Whatever the intention, it is happening and it is real. Maybe Adobe did not intend for Adobe Captivate to be used with SharePoint. It is issues like the one above that cause user frustration. JSON files just simply cannot be deleted and expect the project to function. See the example image below of Adobe Captivate HTML5 Output in the dr folder. Also, there is the main imgmd file that stores png files, text captions, smartshapes, and etc. You may have seen the files labeled as im1, im2, im3 and so on. In more recent versions of Adobe Captivate such as 20, the images are now stored inside of JSON files. However, SharePoint had no issue accepting these files because they were not stored in JSON. There could be hundreds of images in that folder. In the previous versions of Adobe Captivate such as 7, 8, and 9 (before updating to version 9.0.2.437) the individual loose files such as png, smartshapes, and text captions from the project’s HTML5 output were stored in the dr folder. However, it is the way in which the JSON files are now being used that is causing the issue. Why did Adobe decide to use JSON files? A thought is that the HTML5 publishing process generated so many loose file types to the dr folder that Adobe used the JSON format to store these files in a more efficient way. As a result, less tech-savvy users find themselves reaching out elsewhere for support. However, sometimes neither of the before mentioned actions resolve the issue. Then do the same with the JSON files themselves.

See Upload an Adobe Captivate published output on SharePoint for more information.Īnother workaround is to go into the index.html file and replace the JSON extensions with. Normally the SharePoint Administrator can configure the server to allow a MIME type to support JSON format. This issue is affecting users on personal and business levels. The issue Adobe Captivate 2019 users seem to be experiencing is uploading the JSON files included in the project’s HTML5 output to SharePoint. JSON is text, written with JavaScript object notation.JSON is a syntax for storing and exchanging data.This occurs on both intranet and extranet server side.Īccording to (visit for detailed information): Recently there have been some discussions about the JSON files in Adobe Captivate 2019 and issues with SharePoint blocking them during the upload process. The post HTML Slides invisible/missing in published/preview Content appeared first on eLearning.

Any thoughts? I would greatly appreciate your help. Using the browser inspector reveals that the material is there in the DOM. I do not experience any of this in the SWF version. My thoughts are that the error stops subsequent material from loading or everything is set to invisible for some reason. This error is what pops up in the console: The SWF output contains the entire course (136 slides) but the HTML5 output stops at slide 40 and simply shows the background. After that point, the course shows the background only and the console has an object undefined error (Tested in Chrome Version. It seems as though my HTML5 output only publishes the first 20 slides then shows nothing but the background. I am using CP8 (Version 8.0.3.290) to create and publish a SCORM course.

Adobe captivate 8 tutorial