IE11 Security Problems With Custom Certificate
Mar 25, 2015
Hello,
I am having trouble correctly displaying a course completion Certificate in IE11. (I'm using the method described here.) After course completion the student can press a button to get a custom certificate with his/her name on it. The button triggers the following piece of JavaScript:
var newWin=window.open("report.html", "Kursintyg");
The report.html certificate then displays the name variables like so:
<script>
var player=window.opener.GetPlayer();
var fornamn=player.GetVar("Förnamn").replace(/(\r\n|\r|\n)/g, '');
var efternamn=player.GetVar("Efternamn").replace(/(\r\n|\r|\n)/g, '');
</script>
<script>document.write(""+fornamn+" "+efternamn+"");</script>
This works perfect seemingly everywhere EXCEPT when running the Flash version on IE11 at my office (the HTML5 version is working fine). The certificate only reads "undefined" "undefined".
I'm guessing it has to do with some corporate security policy because the variables show up all right on my home computer running IE11. As well as in Firefox and Chrome. Any suggestion what can be done? I need to get it to work on similar corporate computers, because that's the environment where the course is going to be used. I've worked on this all day and I'm getting desperate...
Thanks.
3 Replies
I've tried changing the trigger script to
to see if the variables get passed on to the certificate all right that way (a dirty method, I know), but IE11 refuses to run the script. It seems it doesn't like the questionmark inside the window.open command.
I solved the problem by putting a JavaScript on the HTML certificate, displaying a pop-up asking the student for his/her name again on load (if the strings are empty) before printing it out on the certificate. It's not an elegant solution, and it can be abused, but it will have to do.
Hi Andreas,
Thanks for continuing to share your solution here as I'm sure it's something other users may benefit from as we can't support custom certificates or javascript.
This discussion is closed. You can start a new discussion or contact Articulate Support.