Forum Discussion
Personalizing goodbye.html
Hello,
At the end of exported trainings, a goodbye.html file is displayed.
We modified it to fit our brand chart in a file out of the program folder because we don't have admin rights and asked a sysadmin to make a symbolic link in place of the original file, and were having no problems with it until latest update.
In the latest update, at the 1st launch of the day, an automatic file check puts a new goodbye.html in the program folder and it replaces ours in the SCORM exports :(
It would be cool to have a setting somewhere where we could choose our own goodbye.html file, because now we have to replace original file by ours each day, requiring admin rights.
Edit : nope we can't do that as SCORM exports freeze at the end now, so only solution for now is replacing the goodbye file in each export :(
Regards,
Michael.
2 Replies
Hi MichaelDufour-7,
Happy to share some insight on this.
Currently, Storyline authors can customize or suppress the goodbye.html page. However, some knowledge of JavaScript or HTML is required.
It sounds like you're looking for a built-in Storyline feature that lets you control that design more easily. Thanks for letting us know that level of functionality is important to you.
I'd love to include a bit more context for our product team. About how many SCORM exports are you currently managing where the goodbye.html needs to be modified? Are you able to quantify how much time you and your team spend on these post-publishing updates?
Hi Steven,
As admin rights are required to modify the stock goodbye.html page (I work for some french hospitals so security on our laptops is quite heavy), we deleted it with our IT support team, and in place put a symlink to a file placed in a folder that doesn't need admin rights to edit.
It was working fine until latest update it seems, that will recreate the stock file in the stock folder and won't use our symlink anymore.
If we edit the stock file to put our modified html code in it, SCORM exports will never come to an end, so we need to keep the stock file, and for each SCORM export manually replace the goodbye.html in the zip archive.
That's a page seen by every end user (for some elearning we sometimes have thousands of users) so it should be easily editable/replaceable with something personalized to our style guidelines.
Like just a "path to goodbye.html" field in Storyline export settings so we just edit it one time and don't have to think about it anymore.
Michael.
