Hide Final Replay Button in Microlearning (a "post-publish hack")
For some microlearnings, it is desirable to remove the replay/restart button at the very bottom, especially when Theme -> Navigation is set to Continuous (this results in a large replay button that is the full width of the page).
I just tried the following method - seems to work fine:
The steps for removing the replay/restart button at the bottom of the microlearning are the same whether you are publishing to SCORM or Web:
1. Publish the Rise course (to either Web or SCORM)
2. Go the the folder on your local drive where the web .zip file was saved
3. Unzip the file (e.g. right-click on the .zip file, select "Extract all")
4. In file explorer, go into the unzipped folder
5. Open "index.html" in Notepad:
If published to SCORM, go into "scormcontent" folder to find index.html
If published to Web, go into "content" folder to find index.html
6. With index.html open in Notepad, search for TODO (this will be in the <style> section, just above @media)
7. Copy this text:
.blocks-lesson-restart-button { display: none;}
8. Paste the copied text into the blank line just above @media - your file should look like this:
/* TODO: probably need a way to create a 5-10% darker/lighter color */ .brand--linkColor a:hover, .button.brand--background:hover { opacity: .65 !important; }
10. Back in file explorer, IF YOU PUBLISHED TO SCORM AND ARE IN THE "SCORMCONTENT" FOLDER, go up to the parent folder.
11. Either copy the files/sub-folders to the final deployment location, or do the following:
zip all files & sub-folders
If SCORM, ensure you see "meta.xml" when you zip
If Web, ensure you see "index.html" when you zip
Upload the resulting SCORM .zip file to your LMS.
I've only tested this once so far - so be sure you test it yourself (and don't blame me if it ain't perfect yet!). Also, in the past I have noticed that "post-publish hacks" like this can stop working with the next update/release of Rise. Previously published courses continue to work as predicted, but the "hack" may not work when applied to newly published courses. In this case, I've had to analyze the Rise published files and try to figure out what changed, and modify the hack accordingly.
4 Replies
Hi,
There isn't a way to remove the "replay" bar that I'm aware of.
Hide Final Replay Button in Microlearning (a "post-publish hack")
For some microlearnings, it is desirable to remove the replay/restart button at the very bottom, especially when Theme -> Navigation is set to Continuous (this results in a large replay button that is the full width of the page).
I just tried the following method - seems to work fine:
The steps for removing the replay/restart button at the bottom of the microlearning are the same whether you are publishing to SCORM or Web:
1. Publish the Rise course (to either Web or SCORM)
2. Go the the folder on your local drive where the web .zip file was saved
3. Unzip the file (e.g. right-click on the .zip file, select "Extract all")
4. In file explorer, go into the unzipped folder
5. Open "index.html" in Notepad:
6. With index.html open in Notepad, search for TODO (this will be in the <style> section, just above @media)
7. Copy this text:
.blocks-lesson-restart-button { display: none;}
8. Paste the copied text into the blank line just above @media - your file should look like this:
/* TODO: probably need a way to create a 5-10% darker/lighter color */
.brand--linkColor a:hover,
.button.brand--background:hover { opacity: .65 !important; }
.blocks-lesson-restart-button { display: none;}
@media (min-width: 47.9375em) { /* 768px */
.brand--min768--background { background-color: #5F6369 !important; }
.brand--min768--border { border-color: #5F6369 !important; }
.brand--min768--color { color: #5F6369 !important; }
}
9. Save the index.html file and close Notepad.
10. Back in file explorer, IF YOU PUBLISHED TO SCORM AND ARE IN THE "SCORMCONTENT" FOLDER, go up to the parent folder.
11. Either copy the files/sub-folders to the final deployment location, or do the following:
I've only tested this once so far - so be sure you test it yourself (and don't blame me if it ain't perfect yet!). Also, in the past I have noticed that "post-publish hacks" like this can stop working with the next update/release of Rise. Previously published courses continue to work as predicted, but the "hack" may not work when applied to newly published courses. In this case, I've had to analyze the Rise published files and try to figure out what changed, and modify the hack accordingly.
Thanks, I'm going to give it a try! I do something similar for regular Rise modules, to get rid of the standard headers.
Question—My file seems to have an extra bracket, where should I paste your code?
In new line just above the first "@media" (see attached).