Forum Discussion
Storyline 3.18.28642.0 publishing breaks tincan tracking -- forbidden
I was told to get this new version because of these threads: https://community.articulate.com/discussions/articulate-storyline/firefox-is-it-compatible-or-not
Now when I publish for tincan, my tracking doesn't work. Going through fiddler I see that my tincan tracking statements are getting 403 forbidden errors, so my tracking methods are not getting called. Using published files from my older version - 3.15.26826.0 -- works fine. They return 204, my methods get called and all is good. What changed?
A couple of notes:
- The tincan.xml files produced by each version are identical
- I notice that when publishing in the new version, the dropdown says xAPI instead of tincan. Does this mean there are other differences?
Thanks
Hello Frank,
Sorry to hear that you ran into this snag!
Looks like you've already tested the issue quite a bit on your end. I went ahead and opened a support case on your behalf so our support engineers can do further testing to see why your courses are not working properly when published using the most recent versions of Storyline 3. One of the troubleshooting steps that will be recommended is to test the behavior in SCORM Cloud. Here's how to test this behavior if you want to do this ahead.
Your case is in good hands, and someone from our team will be in touch with you shortly!
- FrankSiegelCommunity Member
Thanks a lot. Just wondering, in the meantime, is there a version between 3.15.26826.0 and 3.18.28642.0 that might be available that I could test with? I couldn't really find any other versions on the website except for the latest. I need a version that will fix the Firefox version but not break our tracking.
- FrankSiegelCommunity Member
I meant "I need a version that will fix the Firefox issue but not break our tracking."
- Jürgen_Schoene_Community Member
can you downgrade to 3.15?
if yes, create a small course with some xapi tracking and upload here the zip of the published folder
then I can to try to patch the firefox problem for version 3.15 (there should be only two quotation marks too many)
UPDATE: add an audio file on the first slide
- FrankSiegelCommunity Member
Thanks Jurgen. For now, I think I'll wait for the support case to play out. Maybe that can fix anything and you won't have to patch. What I was wondering about in the meantime though, was that I know there is a version 3.16.27367.0 out there. I was going to try to test things out on that, but I don't know how to get that version. Thanks
Hi Frank!
You can install a previous version of Storyline 360 by opening your Articulate 360 desktop app.
- Select the arrow next to Storyline 360, then select Other Versions.
- Select Install on the version you would like. It's important to note that this list will include all the versions released in the past six months.
I see that you're working with my teammate, Luiza, in a support case, so we'll continue the conversation there!
- FrankSiegelCommunity Member
Hi Kelly. I'm running Storyline 3. With the desktop app I'm running, I don't really see any way to get another version. I looked on the website didn't seen the interim versions. I guess I'll just wait for the support case to be resolved, unless you have another way to get this. Thanks
- FrankSiegelCommunity Member
It looks like 3.19.29010.0 has fixed my tracking issue. Also, when I run a course in Firefox, it starts up and runs. However, on the Results slide, I have a trigger that executes a javascript function called track_completion. However, in Firefox, it doesn't run. When I look in the console, I get this: actionator::exeJavaScript - track_completion is not defined
Other browsers run completely. I'm sure this is a Firefox issue. Has anyone in the Articulate community seen this error when running javascript? Thanks a lot.
- Jürgen_Schoene_Community Member
where is "track_completion" defined
- in a separate javascript script file?
- in the start html file?
- in a trigger "on timeline starts"?
- ... - FrankSiegelCommunity Member
It's a trigger when you hit Next on the results slide. It is in a separate javascript file in our system. That script is found because of these statements in our aspx module that runs our training:
<script type="text/javascript" src="/js/track.js"></script>
function injecttracking() {
var head = this.contentDocument.getElementsByTagName("head")[0];
var scr = this.contentDocument.createElement('script');
scr.type = 'text/javascript';
scr.src = '/js/track.js';
head.appendChild(scr);
}
window.onunload = reloadParent;
$(function () {
$('iframe').on('load', injecttracking).on('unload', reloadParent);
});Other browsers find it just fine. Only firefox has the issue.