Skip to main content
Participant
May 31, 2017
Question

Missing fluid boxes when viewing published output

  • May 31, 2017
  • 2 replies
  • 327 views

I just completed converting a legacy Captivate 9 module to responsive using Captivate 2017 (Trial). Everything works when the project is previewed in Captivate 2017 but when published, all content placed in fluid boxes end up missing. I tried uploading the published file in our LMS but the same issue persists. Is there a setting that I missed somewhere or is this really a limitation of the trial version? I am hoping that I could make this work as the module in question will be used to build a business case to upgrade from Captivate 9 to 2017. Thanks!

    This topic has been closed for replies.

    2 replies

    zeeshan hussain
    Adobe Employee
    Adobe Employee
    May 31, 2017

    Hi,

    Please drop a mail to CaptivateHelp@adobe.com and share your project using drop box or google drive. We will get this checked.

    Regards,
    Zeeshan

    RodWard
    Community Expert
    Community Expert
    May 31, 2017

    It's not a limitation of the Trial version.  There must be another reason.

    Try uploading the same SCORM module to SCORM Cloud and test it there.

    jlpalomaAuthor
    Participant
    June 2, 2017

    Thanks for your response, Rod. I previewed the project in SCORM Cloud and it worked. However, the same is not the case in our LMS. I also came across your blog about publishing for mobile devices and your point about removing all Flash elements of the project led me to think that it could be causing my issue. When I expand the published .zip file, there is a filename with the .swf extension.  I don't know why this happens since I have removed all .swf elements in the project (the HTML Tracker no longer shows incompatible elements) as suggested in your blog. Could it be because this started as a legacy project created in Captivate 9 and then converted to responsive using Captivate 2017? I hope I wouldn't have to recreate the whole project from scratch in Captivate 2017.

    RodWard
    Community Expert
    Community Expert
    June 2, 2017

    From the dates shown on that SWF file I would say the SWF and a number of other files there are relics of a previous publish run.

    If you have now converted this project over to HTML5 responsive with Fluid Boxes then these files should not be present.

    I suggest you republish the project again and this time make sure the target folder is empty.

    With the issue on your own LMS working differently to SCORM Cloud, check with your LMS server administrator to find out if JSON mimetype is enabled on the server.  It is in SCORM Cloud but it's common for it NOT to be enabled on other LMSs.  It's been a requirement for Captivate HTML5 output since late versions of Cp9.