White Screen Error

Unknown

Hello

I have a problem. I have an e-learning course, part of the course involves pressing enter after keying in data to move to the next screen.

The first time they press enter to move to the next screen it works fine. But the second time they press enter to move to the next screen, if they are using Internet Explorer, the whole screen goes white, and does nothing. If they are using Google Chrome it works fine. It also works fine in my Lectora preview.

I have tried changing the emphasis (for example, instead of 'on Enter go to Next Page', I changed it to 'on Enter go to {specific page name}' but it still has the same problem.

It also seems to have just started today (and the project goes live tomorrow - typical).

Any wisdom would be greatly appreciated (it might even have nothing to do with pressing enter).

Simon

jvalley4735

For reference what version of IE are you previewing in?  Are you running in compatiablity mode? Are you experiencing the issue when you preview using F9 or after publishing to SCORM or HTML or both?  Can you share the files? If your not comfortable attaching them here can email them to me at [email protected] I won't share them with anyone other then the dev or support team if I need their help resolving the issue.

ssneg

Do you see any JS errors in dev console (F12)?

Unknown

The IE version is IE9. I have tried it in compatibility mode and it doesn't make a difference.

I have tried it in Firefox and it worked fine.

I have tried a different method of moving between the pages (from pressing ENTER to clicking onto a next button) and it still comes up with the white screen.

The problem occurs when viewing the course through CourseMill wave (in IE9)

Unfortunately I do not know JavaScript (It's on my to do list :-) ) So I am not sure whether there are any JS errors.

ssneg

This article explains how to view errors in IE9. You don't have to understand the errors, just copy the text or show a screenshot.

I'll try to replicate this scenario on my own, too, when I have a chance.

jvalley4735

My inside source suspects a JS error as well.  If possible, can you send it into Support for them to look at?  [email protected]

Unknown

Hi Jennifer. I will send it in to support to look at now.
Been real busy with back to back training for a while.
Thank you again.
Kind regards
Simon

shannon7305

Simon,

I am with Trivantis Support.  I am going to create a support case for you.  We can correspond via the email case and assist with troubleshooting.

Unknown

Thank you Shannon
I have sent the course into [email protected]
Kind regards
Simon

Unknown

Hello

So I have sent my course to Trivantis support, but they are now asking for my login details for Lectora Online so that they can replicate the problem.
Is this normal? they should be able to replicate the problem without my credentials.
Kind regards

Simon

jvalley4735

In cases where the trouble is really hard to replicate the support team may ask for your login information. This way they can try to replicate the issue on a computer setup similar to what you have. Hopefully she'll be able to resolve it by either using the file you provided or by scheduling a screen sharing session.

dmattos8952

Hello Simon:

HTML extensions are very powerful. As the saying goes, with (great) power comes (great) responsibility. Lectora will happily pass along to the published page whatever you write on the input box without any validation or security check.

In this case, you left an unmatched <style> tag inside a HTML Extension, modern browsers were able to parse the HTML despite that problem, even IE8/IE9 worked within an independent HTML page, however it inconsistently failed within HTML frames, which Cousemill Wave, and most LMS, relies upon.

The lesson is - be very careful when using HTML Extensions, specifically on how you use matching HTML tags. Depending on the error, a Lectora page will fail, not show or even partially work.The worse part is that, different browsers will parse the HTML code differently, so unexpected problems can show up only on certain client browsers, usually IE. Older versions of IE fail in weird and surprising ways!