Turn off Restricted or Locked navigation without republishing.
Mar 16, 2015
I have a course posted on our web server that has Restricted navigation. It is published already and on the web server. I want my reviewers to look at it, but I want them to be able to jump to the quiz - I don't want to force them to go slide by slide. What to do? Well, I could republish the entire course and reupload, or, here's another idea:
Go into the story_content folder of the published course, and find a file called frame.xml. Open this in a text editor (Notepad for example), and find this statement:
<option name="flow" value="restricted" />
Change "restricted" or "locked" to "free":
<option name="flow" value="free" />
Now reupload the file, replacing the frame.xml file on the web server.
Now your reviewers will be able to jump around.
When you want to put the navigation restrictions back in place, just upload a version of frames.xml where the value is "restricted" or "locked"
11 Replies
Here is also how to lock/unlock the seekbar:
(In Dreamweaver you can open the frames.xml file and then click Commands > Apply Source Formatting to make the XLM readable like this)
Thanks Will for sharing that here and offering users another alternative.
Should that setting by itself also be impacting the HTML5 view of the course? I applied that as shown above and it works great in the Flash player but the HTML5 player still behaves as originally published.
Hi Bernd,
I'm not sure that Will is subscribed to this thread, but since it's a modification of the published output it's something I won't be able to assist with. You could use the "contact me" button on his profile to reach out directly.
Ashley, I'm a little confused. I'm not sure how I could help with this either. If the HTML5 version of the course doesn't conform to the settings in the frames.xml file, then it seems to me that this is something an Articulate developer would need to fix. Maybe the settings are defined somewhere else for the HTML5 version of the course. I have no idea. My reviewers have Flash so it isn't something I'm that worried about.
Hi Will,
I'm unsure to the change you made in the published output and can't support it although I don't know what would be wrong in the XML file? We'd want to take a look at a course within the .story file to see the different behavior when publishing to HTML5 and testing the Flash and HTML5 content once it's loaded in the entire environment.
I am just now realizing that modifying this free/restricted/locked setting in frame.xml only works for the flash output. The HTML5 output still has the same issue and I am unable to correct it in the files. Are we unaware of an HTML5 equivalent of changing this setting?
Hi Eric,
This thread is a bit older so I dont' know if other users are still subscribed but you may want to send them a message using the contact me button on their profile, as our team is unable to assist with the modifications to the published output or changes within the code of published files.
For HTML5 output :
Thanks Daniel! I was able to change the flow to 'restricted'.
Only thing is... I also need to know how to 'Restrict Next/Prev Buttons'. Is it possible to do that without republishing?
Hello,
The Restricted state is for menu only.
For Next/Prev Buttons your options are "readonly":false/true ... and allow drag after completion, which I don't know the correspondence in the frame.js file or elsewhere (it requires some research).
dB.
This discussion is closed. You can start a new discussion or contact Articulate Support.