I built a learning course using articulate storyline. I added a print button at the end of quiz activity. The print function works fine with HTML5 output format. But if I publish the course in SWF format, the print button won't work. Can anybody help me to fix the problem?
First, can you tell me how you're viewing the published presentation, please? Are you viewing the published output files locally, or are you uploading to a web server or LMS?
If you're viewing your published files locally, this may be the problem. If you view a published Storyline presentation on your local hard drive or send it to someone else to view on their local hard drive, you'll encounter security restrictions from the computer, web browser, Flash Player, and network that'll cause various features of your content to fail.
To properly test your published content and share it with others, upload it to the environment for which it was published. Please review the article below for more information:
I suggest using SCORM Cloud for your course - it's a great place to test SCORM content.
Another option would be to use our Tempshare server. Just keep in mind that this server is only available for testing content - it is not officially supported by Articulate and all content will be removed automatically after 10 days.
You're always welcome to try out Articulate Online, as well - it's available for a free 30 day trial.
We're experiencing the same issue. On final screen, we've called javascript code to print the screen but what it does print only an empty page. Here is the url to test it -
Hi Musa! This thread is a bit dated. Perhaps someone in the community will be able to assist you with your JavaScript coding if that is the issue with your course.
Thanks Leslie, My problem exists only in chrome and Firefox. Stuck for an week. Don't know the solution yet! Just wonder why articulate doesn't has print slide feature?
There is a feature to print the results slide of a project as you can see here. I cannot see the course that you are sharing to know if this is the method that you are utilizing or not.
You mentioned JavaScript coding, so I assume you are looking for another solution.
I cannot speak as to why a feature is not included, but if this is a feature you would like to see, you are welcome to share your thoughts with our development team here.
Hi, I have sort of like the same issue. When publishing the content via Web everything works fine, the print button works and the information typed into the Text Entry Field shows on the printout. However, when publishing as LMS and saving the zip file in the server platform the print button does not show what is typed in the Text Entry Field, it only shows the background and that's it.
Since you published for LMS, have you tried testing it in a LMS environment like SCORM Cloud? If so, are you getting the same results? We generally use SCORM Cloud since it's industry standard for LMS testing to parse out file issues versus LMS issues. We are happy to help you with that testing if you'd like to share your file!
Found the problem and fixed it. Not sure if it's a compatibility issues with our SCORM platform but it is working now, just had to go through a lot of trial and error. Thanks.
9 Replies
Hi Alice,
Welcome to the community!
First, can you tell me how you're viewing the published presentation, please? Are you viewing the published output files locally, or are you uploading to a web server or LMS?
If you're viewing your published files locally, this may be the problem. If you view a published Storyline presentation on your local hard drive or send it to someone else to view on their local hard drive, you'll encounter security restrictions from the computer, web browser, Flash Player, and network that'll cause various features of your content to fail.
To properly test your published content and share it with others, upload it to the environment for which it was published. Please review the article below for more information:
Publishing and Sharing Articulate Storyline Content
Let us know if you see any improvement!
Best,
Christine
Hi Christine,
We're experiencing the same issue. On final screen, we've called javascript code to print the screen but what it does print only an empty page. Here is the url to test it -
http://bit.ly/1g4WUqc
We're stuck for a while, could you guys help us?
Thanks
Musa
Hi Musa! This thread is a bit dated. Perhaps someone in the community will be able to assist you with your JavaScript coding if that is the issue with your course.
Thanks Leslie, My problem exists only in chrome and Firefox. Stuck for an week. Don't know the solution yet! Just wonder why articulate doesn't has print slide feature?
There is a feature to print the results slide of a project as you can see here. I cannot see the course that you are sharing to know if this is the method that you are utilizing or not.
You mentioned JavaScript coding, so I assume you are looking for another solution.
I cannot speak as to why a feature is not included, but if this is a feature you would like to see, you are welcome to share your thoughts with our development team here.
Hi, I have sort of like the same issue. When publishing the content via Web everything works fine, the print button works and the information typed into the Text Entry Field shows on the printout. However, when publishing as LMS and saving the zip file in the server platform the print button does not show what is typed in the Text Entry Field, it only shows the background and that's it.
Hi Jan,
Since you published for LMS, have you tried testing it in a LMS environment like SCORM Cloud? If so, are you getting the same results? We generally use SCORM Cloud since it's industry standard for LMS testing to parse out file issues versus LMS issues. We are happy to help you with that testing if you'd like to share your file!
Hi Alyssa,
Found the problem and fixed it. Not sure if it's a compatibility issues with our SCORM platform but it is working now, just had to go through a lot of trial and error. Thanks.
Glad you're back up and running, Jan. Thanks for the update!
This discussion is closed. You can start a new discussion or contact Articulate Support.