Follow the on-screen instructions to complete the installation.
Enter the Adobe ID and password for the account for which you have an active subscription to Adobe Captivate. During installation, you would be prompted to sign in using your Adobe ID.
Once the files are completely downloaded, double-click to start the extraction and follow the on-screen prompts to install the product.
To upgrade your subscription, follow the steps below: If you have an active subscription for Adobe Captivate, you are eligible to upgrade to the recently released 2017 release of Adobe Captivate as part of your subscription. Image, (2018), “ Adobe Captivate HTML5 Output in dr folder” by Veem. , (2018), “ JSON – Introduction”, Retrieved on November 4, 2018, from Īdobe, (2018), “ Upload an Adobe Captivate published output on SharePoint” Retrieved on November 4, 2018, from 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.