please tell me what computer you are using while working with Storyline.
Perhaps with model name or link to a shop.
I am using Storyline 3 for a few years now. All is great.
BUT one thing is a nightmare for me. Big quizzes I create (50-80 questions) as xAPI-files are causing errors in the developer console of Chrome. Therefore these xAPI-modules don't set themself on complete on my wordpress lms. I tried many times recreating them, following the guidelines around "broken" storyline files.
Hi Thomas, that could be an expensive experiment. Id explore the errors first, maybe report those here if not already done. This is something I may be able to help with. I have a powerful system and have experience with xAPI too, so if you would like me to try publishing and testing your content I can do that for you.
I used a wrong profile while creating this Thread. So, here I am ;) Shall I send you the original storyline-file via private message?
Yes, I reported it here in many ways. I worked more than one year on my online course. Now it is live and consisting of 38 xAPI-files, all hosted in learndash (Wordpress-LMS). Grassblade LRS is responsible for LRS-Reporting.
Main Problem currently I got no solution for: Completed-Status is not always posted to the LMS xAPI-files have errors in the Chrome Dev Console
Even I recreated freshly many time the xAPI-files (that took me months) and paying attention to these guidelines:
Only worked on local Drive
Alway zipped SL-files before uploading or sending via mail
Shortened my file-names
Removed all characters out of my file-names except letters and figures
Never let SL-file open while not working on it
Stored different version after any edit
Never copied elements from one SL-file into another
Always pasted text first into windows-editor to remove text formatting if I pasted text into a slide
I edited the fresh new created files, after every 60 mins. I published them, tried them with Chrome, while developer console was open. No errors. Then out of the sudden HTML, JS, or other errors appeared in the console. And I did follow the above guidelines and did nothing other.
I don't think all content of Storyline 3 tool has this issue, because I have not seen this same issue for any other customer, and we have thousands of customers using Articulate tools.
I think there is some issue in the content you have added. May be it is related to some text or content, or related to some Animation in the slide.
I think you must try to fix one content, and find the real reason behind the issue. Then spend time on other content.
Hi Thorsten, can you confirm if the errors are occurring when the content is launched, or are they triggered by a particular procedure running?
And you are also confirming that the files have not changed, and the error just started to occur one day?
Can the error be replicated in other browsers too?
Thorsten, you can contact me privately if you wish to share access to one of the problem files. Just click on my profile and you can message through there.
Hi Thorsten, can you confirm if the errors are occurring when the content is launched, or are they triggered by a particular procedure running? Usually in the course of the modul not at start. As there have been so many different errors in different modules it seems they mostly appear on result slides even if they are a preliminary and not the final result slide.
And you are also confirming that the files have not changed, and the error just started to occur one day? No, the errors always appeared after editing and publishing out of SL. Not without editing.
Can the error be replicated in other browsers too? I got customers, the ones with firefox and safari browser are complaining about the modul not being set to complete. The customers with chrome have to restart the completed module a second time, choose continue, they see the result slide again of course, and have just to close it again and then the status is posted to the LMS.
Thorsten, you can contact me privately if you wish to share access to one of the problem files. Just click on my profile and you can message through there. I will. Thanks for your time.
Hi Thorsten, I wasn't able to produce any errors in SCORM Cloud with the file you sent me. It wasn't tracking a great deal, just registering "Experienced" for each slide.
It sounds like the issues you having aren't trivial and will take significant investment in time to resolve for an experience developer with access to your system and content so they can work with you closely and debug the issues.
5 Replies
Hi Thomas, that could be an expensive experiment. Id explore the errors first, maybe report those here if not already done. This is something I may be able to help with. I have a powerful system and have experience with xAPI too, so if you would like me to try publishing and testing your content I can do that for you.
Dear Sam,
I used a wrong profile while creating this Thread. So, here I am ;)
Shall I send you the original storyline-file via private message?
Yes, I reported it here in many ways. I worked more than one year on my online course. Now it is live and consisting of 38 xAPI-files, all hosted in learndash (Wordpress-LMS). Grassblade LRS is responsible for LRS-Reporting.
Main Problem currently I got no solution for:
Completed-Status is not always posted to the LMS
xAPI-files have errors in the Chrome Dev Console
Even I recreated freshly many time the xAPI-files (that took me months) and paying attention to these guidelines:
I edited the fresh new created files, after every 60 mins.
I published them, tried them with Chrome, while developer console was open.
No errors.
Then out of the sudden HTML, JS, or other errors appeared in the console. And I did follow the above guidelines and did nothing other.
A Grassblade LRS expert wrote to me:
I still see the errors when I launched two contents:
See: https://screencast.com/t/1ikGOgGnUB
I don't think all content of Storyline 3 tool has this issue, because I have not seen this same issue for any other customer, and we have thousands of customers using Articulate tools.
I think there is some issue in the content you have added. May be it is related to some text or content, or related to some Animation in the slide.
I think you must try to fix one content, and find the real reason behind the issue. Then spend time on other content.
Hi Thorsten, can you confirm if the errors are occurring when the content is launched, or are they triggered by a particular procedure running?
And you are also confirming that the files have not changed, and the error just started to occur one day?
Can the error be replicated in other browsers too?
Thorsten, you can contact me privately if you wish to share access to one of the problem files. Just click on my profile and you can message through there.
Dear Sam,
my answers below your text.
Hi Thorsten, can you confirm if the errors are occurring when the content is launched, or are they triggered by a particular procedure running?
Usually in the course of the modul not at start. As there have been so many different errors in different modules it seems they mostly appear on result slides even if they are a preliminary and not the final result slide.
And you are also confirming that the files have not changed, and the error just started to occur one day?
No, the errors always appeared after editing and publishing out of SL. Not without editing.
Can the error be replicated in other browsers too?
I got customers, the ones with firefox and safari browser are complaining about the modul not being set to complete. The customers with chrome have to restart the completed module a second time, choose continue, they see the result slide again of course, and have just to close it again and then the status is posted to the LMS.
Thorsten, you can contact me privately if you wish to share access to one of the problem files. Just click on my profile and you can message through there.
I will. Thanks for your time.
Hi Thorsten, I wasn't able to produce any errors in SCORM Cloud with the file you sent me. It wasn't tracking a great deal, just registering "Experienced" for each slide.
It sounds like the issues you having aren't trivial and will take significant investment in time to resolve for an experience developer with access to your system and content so they can work with you closely and debug the issues.
This discussion is closed. You can start a new discussion or contact Articulate Support.