I have created a small tutorial screencast integrated with regular storyline files and when I publish the file for the web it works fine. The problem comes when I zip the file, extract the files and click on the story_html5.html the screencast becomes blurry and if there are boxes to highlight certain areas they move out of place. Is there something else I should be doing when publishing this because the tutorials will be hosted on the web and the developer said they must link to the story_html5.html file in order to make it work.
Have you tried testing the published output in Tempshare? Just drag the zipped file into the box, and Tempshare will do the rest. Once the file is ready, click View, and a new tab will open with a link to your file. You may notice that the link defaults to story_html5.html depending on the browser you use. If it defaults to story.html, just change the end of the URL to story_html5.html, and you'll see the HTML5 version.
Hello Susan! Just to chime in with Alyssa, it sounds like your developer will want the ability to launch the HTML5 output of your published project. That shouldn't be a problem!
From what you're describing, it sounds like you might be launching your course from the published output folder. Instead, you'll want to load that output onto a web server (like Alyssa describes above) and view your content online. You'll get the best idea of how the content will play (especially if you want to link directly to the HTML5 output) in its intended environment. Here's some further information about how to view your project after publishing.
If you've loaded it onto a web server, you can use these browsers to view that output:
Windows: Google Chrome (latest version)
Mac: Safari 7 and later, Google Chrome (latest version)
Mobile: Safari in Apple iOS 7 and later, Google Chrome (latest version) in Android OS 4.1 and later
If you're following those practices, and still getting that weird behavior, we'd be happy to help you test out your file! You can share it here in the discussion (.story file) or in a case with our engineers. Either way, we'll work with you to get your project running smoothly.
Thanks for your quick replies, but unfortunately the developers still cannot get it to work. I think they are taking the zip file (unzipping it) storing that file on their server (it is for a specific tool) and then using a link for the story.html file (they have also tried with the html5 file as well.
I am new to Articulate with my first project and I am encountering a similar error. I published the project using the "Web" option with all the default settings that came with it. After it has been published successfully, I emailed the file from that publish window to a colleague. The email came with instructions on how to save the zip file and which file she should open the project. When she tries to save it, it gave her this error, "Save Failed, Invalid Form ($BODY is not in rich text). However, I followed the same instructions and it was not giving me this error and it played fine. Any ideas why my colleague gets the error? Thanks
Ah jeez, ok. Sorry that they're getting stuck, Susan. A couple of follow up questions for you, then:
When you publish and zip, are you zipping the project from within Storyline?
Also, when the developers are taking your zipped file and extracting, they'll want to be sure to not change the file structure in any way and upload everything to the server. I know you're a bit removed from the process on that end, but this article discusses uploading your content to a web server in general.
You mentioned that it is working fine when you publish for web-- just to confirm, you're able to host and launch the project successfully on another site? If the project works fine somewhere else, maybe a screencast of their process for uploading the content to the other server would be helpful for the community to further troubleshoot.
That's not an error I've seen before specific to Storyline or Articulate so I did a quick Google search on it, and it returned a number of pages about Lotus Notes and issues on the client/email server. Beyond that it was a bit Greek too me - but I'd look at having your colleague confirm that they are saving the initial zip file locally, extracting and then trying to run the story.html file - they'll need to have a browser client installed as well (Chrome, Firefox, Internet Explorer, etc.). I'd also suggest taking a look at sharing the published copy with them on a web server as there are some known issues with viewing content locally regardless of that error message that you'll see described here a bit more. That article also includes some recommendations of where you could share.
6 Replies
Hi Susan!
Have you tried testing the published output in Tempshare? Just drag the zipped file into the box, and Tempshare will do the rest. Once the file is ready, click View, and a new tab will open with a link to your file. You may notice that the link defaults to story_html5.html depending on the browser you use. If it defaults to story.html, just change the end of the URL to story_html5.html, and you'll see the HTML5 version.
Hello Susan! Just to chime in with Alyssa, it sounds like your developer will want the ability to launch the HTML5 output of your published project. That shouldn't be a problem!
From what you're describing, it sounds like you might be launching your course from the published output folder. Instead, you'll want to load that output onto a web server (like Alyssa describes above) and view your content online. You'll get the best idea of how the content will play (especially if you want to link directly to the HTML5 output) in its intended environment. Here's some further information about how to view your project after publishing.
If you've loaded it onto a web server, you can use these browsers to view that output:
If you're following those practices, and still getting that weird behavior, we'd be happy to help you test out your file! You can share it here in the discussion (.story file) or in a case with our engineers. Either way, we'll work with you to get your project running smoothly.
Thanks for your quick replies, but unfortunately the developers still cannot get it to work. I think they are taking the zip file (unzipping it) storing that file on their server (it is for a specific tool) and then using a link for the story.html file (they have also tried with the html5 file as well.
I am new to Articulate with my first project and I am encountering a similar error. I published the project using the "Web" option with all the default settings that came with it. After it has been published successfully, I emailed the file from that publish window to a colleague. The email came with instructions on how to save the zip file and which file she should open the project. When she tries to save it, it gave her this error, "Save Failed, Invalid Form ($BODY is not in rich text). However, I followed the same instructions and it was not giving me this error and it played fine. Any ideas why my colleague gets the error? Thanks
Ah jeez, ok. Sorry that they're getting stuck, Susan. A couple of follow up questions for you, then:
When you publish and zip, are you zipping the project from within Storyline?
Also, when the developers are taking your zipped file and extracting, they'll want to be sure to not change the file structure in any way and upload everything to the server. I know you're a bit removed from the process on that end, but this article discusses uploading your content to a web server in general.
You mentioned that it is working fine when you publish for web-- just to confirm, you're able to host and launch the project successfully on another site? If the project works fine somewhere else, maybe a screencast of their process for uploading the content to the other server would be helpful for the community to further troubleshoot.
Hi Gaosheng,
That's not an error I've seen before specific to Storyline or Articulate so I did a quick Google search on it, and it returned a number of pages about Lotus Notes and issues on the client/email server. Beyond that it was a bit Greek too me - but I'd look at having your colleague confirm that they are saving the initial zip file locally, extracting and then trying to run the story.html file - they'll need to have a browser client installed as well (Chrome, Firefox, Internet Explorer, etc.). I'd also suggest taking a look at sharing the published copy with them on a web server as there are some known issues with viewing content locally regardless of that error message that you'll see described here a bit more. That article also includes some recommendations of where you could share.
This discussion is closed. You can start a new discussion or contact Articulate Support.