Engage does not open in Firefox (15.0)

Sep 03, 2012

I'n having a problem since a few days my engage content does not play/open in firefox. All other browsers work fine, also did firefox till last week. The Presenter content works fine.

I think it is because firefox is updated, because it all worked fine before, and it is on all pc's that I tried.

Does anyone know a solution?

35 Replies
hans erlandsson

Ok, 

We found a workaround we decided to use which some of you might find useful... However, this is based on that the SCORM-interactions & quizzies WE are using in our LMS is just for general "standalone" rehearsal and that awarded points etc are never communicated into our LMS...  (efront by the way).

Our current webhotell told us which compressionmodules that was used on our server. We tried to modify the .htaccessfile in order to find out how to exclude the compression for XML-files only but failed.

We then uploaded our Engage SCORMzips to a completely different server (cheap webhotel, surftown.se simple LAMP-stack for ~$10/month), unzipped them, used the complete URL to for example engage.html, then added iframetags in our LMS and thereby embedded each and everyone of the SCORMS.

Luckily, we are not able to replicate the intermittent failing Scorm-interactions...

Trying each and every SCORM in scormcloud confirmed that all of them were "OK" and executable, however this "green light" was an illusion due to that the scormcloud-server probably managed to disable the XML-compression - which we never managed to do. Now, hosting the SCORMs at scormcloud failed due to cookies that couldnt be properly set.

I find it hard to believe that our new cheap webhotel isn´t using compression BUT I suspect that they might use other compression modules on the Apache than on our original webhotell (zip and zlib, not gzip). FYI we successfully tried "hosting" our scorms at articulate-online using iframe/embedding, same issue with cookies as scormcloud though.

Now, sorry not to be able to tell more regarding the technical settings - but we are happy as long as it works by this kind of "workaround". Of course, redirecting/embedding all SCORMs was tideous but now at least our ~600 users  are happy...

One problem have however turned into two; the second is of course adressing the lack of a patch/fix etc from TeamAdobeArticulate. 

Nancy Terry

Hi all,

First of all, I'm grateful for this forum - it's incredibly helpful.

I'm wondering if there are any updates on this issue? Our organization is very decentralized and in many cases, users do not have admin rights on their computers so reverting to a previous version of Flash will not be an option. We have a respectable Mac population, and as it occurs on Firefox and Safari, asking them to find a PC in order to use IE isn't really an option for us. Our LMS is hosted by the vendor so addressing the compression aspect is more complicated than just asking them to remove it.

We have been encouraging people to use Articulate because it "plays well" with our LMS, but this issue is coming up more and more, and I'm really hoping there will be a way to address this without having to redo any online training with Engage activities.

Thanks!

Nancy

Nancy Terry

While we've stopped having problems with when running Engage interactions on Firefox using a PC, we're still seeing issues with running Engage interactions on a Mac (with either Firefox or Safari). They still get the "spinning wheel of death" when they get to an Engage interaction within the course. We're hosted by our LMS vendor, so turning off compression isn't possible. Has anyone heard if there been any progress in addressing this issue?

Kevin Thompson

Any updates to the "spinning wheel of death" Engage content problem?

We have some LMS-hosted content that will not load in the latest versions of Firefox and Safari (with latest Flash Player).  Everything works dandy in Chrome (Win & Mac), Firefox (Win), Safari (Win).  No such luck with Firefox (Mac) and Safari (Mac).

Would appreciate guidance!

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