I have a course completion slide at the end. I have disabled the Previous and Next buttons for that slide. Everything works well in Preview and in View Project - no buttons on the last slide. But when I ftp the course up to our test site the buttons re-appear. I have gone over this several times in Firefox, Chrome and Internet Explorer. Same thing. Help please.
This is so weird. Today the problem does not occur in thebrowser. The buttons are gone. Did not recompile or reload. Did clear mybrowser cache yesterday before I ran the course. So I checked with my network admin. He thinks itmight be because I did upload a version with the buttons visible earlier yesterdayand the server cache might have been fetching that version instead of the one Iloaded up later. Since the server cache is cleared every night, now it will befetching the up-to-date version.
Something learned. Thanks for your quick response.
3 Replies
Hi Jason,
Could you share the .story file with us so that we could take a look at it?
Normal 0 false false false
oNotPromoteQF /> EN-US X-NONE X-NONE /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif";}
This is so weird. Today the problem does not occur in thebrowser. The buttons are gone. Did not recompile or reload. Did clear mybrowser cache yesterday before I ran the course. So I checked with my network admin. He thinks itmight be because I did upload a version with the buttons visible earlier yesterdayand the server cache might have been fetching that version instead of the one Iloaded up later. Since the server cache is cleared every night, now it will befetching the up-to-date version.
Something learned. Thanks for your quick response.
Thanks for the update Jason and I'm happy to hear it was something relatively easy to fix.
This discussion is closed. You can start a new discussion or contact Articulate Support.