Opening old player.html files

Dec 09, 2013

I am in the process of updating some old Articulate files that I created several years ago with Articulate Presenter 5.3.  When I open the player.html file of the original classes I created, it won't open.  I have tried it with both Chrome as well as IE 11.  I realize the html code from that file is very old and doesn't take into account newer browsers.  Is there a new player.html file I can use to launch the classes?  I know that if I just open the playershell.swf I can view the class that way.  I'd just rather have an official html file instead of one I write myself if possible.

Thanks!

Nathan 

3 Replies
Christine Hendrickson

Hi there Nathan and welcome to E-Learning Heroes!

I have not personally worked with that version of Presenter. However, it may be an issue of how you're opening that HTML file. It sounds as if you're attempting to open and view the published files locally. Is that right?

Both versions I've worked with produce published output that is best viewed after uploading the output files to a web server or LMS. If you view the published files locally, you'll run into some issues - I'm assuming this is going to be the same for the older version of the output files as well.

If you view a published Studio 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. If that particular project was published for the web, I would recommend uploading it to a web server, just to see if it functions properly. 

If you don't have access to a web server, you could try zipping the files and uploading to Tempshare. However, I cannot guarantee that it will function at 100% once it's uploaded to that server - but it might help :)

Let us know how it goes!

Nathan Harmon

Christine,

It used to work when I published them.  It has to be something with the HTML code.  If you at the HTML, there is browser detection scripting:

// Browser Detection

var IE6Above = false;

var IE7Above = false;

var strVersion = navigator.appVersion;

var nIndex1 = strVersion.indexOf("MSIE") + 5;

var nIndex2 = strVersion.indexOf(".", nIndex1)

if (nIndex1 >= 0 && nIndex2 > nIndex1) { IE6Above = (Number(strVersion.substring(nIndex1, nIndex2)) >= 6); }

if (nIndex1 >= 0 && nIndex2 > nIndex1) { IE7Above = (Number(strVersion.substring(nIndex1, nIndex2)) >= 7); }

var NS4 = (navigator.appName.indexOf("Netscape")>=0 && parseFloat(navigator.appVersion) >= 4 && parseFloat(navigator.appVersion)

var IE4 = (document.all)? true : false;

var NS6plus = (parseFloat(navigator.appVersion) >= 5 && navigator.appName.indexOf("Netscape")>=0 )? true: false;

var isMac = (navigator.appVersion.indexOf("Mac")!=-1) ? true : false;

var IEmac = ((document.all) && (isMac)) ? true : false;

var IE4plus = (document.all) ? true : false;

var IE5 = ((document.all)&&(navigator.appVersion.indexOf("MSIE 5.")!=-1)) ? true : false;

var IE6 = IE6Above;

var IE7 = ((document.all)&&(navigator.appVersion.indexOf("MSIE 7.")!=-1)) ? true : false;

var Safari = (isMac &&(navigator.appVersion.indexOf("Safari")!=-1)) ? true : false;

var Safari3Plus = (parseFloat(navigator.appVersion.substr(navigator.appVersion.indexOf("Safari/") + 7)) > 525);

var Opera7plus = ((document.all)&&(navigator.userAgent.indexOf("Opera 7")!=-1)) ? true : false;

var FF = (navigator.userAgent.indexOf("Firefox")!=-1) ? true : false;

var FF1 = (navigator.userAgent.indexOf("Firefox\/1")!=-1) ? true : false;

var Opera = (navigator.userAgent.indexOf("Opera")!=-1) ? true : false;

var Mozilla = (NS6plus && (navigator.userAgent.indexOf("Netscape")

var NS7_2Plus = false;

var Mozilla1_7Plus = false;

var isLinux = (navigator.userAgent.indexOf("Linux") != -1);

var isWindows = (!isMac && !isLinux)

As you can see we are now way past IE 7 and chrome isn't even mentioned in here at all.  I'm guessing that something with the above code is just so old it doesn't work anymore.
Regards,
Nathan
Christine Hendrickson

Hi Nathan,

I make no claim to be an HTML expert :) We also cannot support modifying the output files.

Perhaps someone with a little more experience with that version or with some coding experience can provide some suggestions that may help.

Also - I still recommend uploading them and trying them on a server. The HTML file can't limit it to those versions - I see the detection code, but I don't think that's a restriction. If nothing else, you could see if it's possible to download one of those versions, if you have no way to upload and test the content. 

Good luck! :)

This discussion is closed. You can start a new discussion or contact Articulate Support.