Menu: Slide numbering errors - back and forth from correct numbering sequence to "chaos"

Apr 07, 2018

Hi,
I am suddenly encountering errors with the Menu item #'s in my Articulate 360 file, published to our LMS provider (Matrix).  Normally when the e-module begins, the Menu slide #'s look like:

  The user would then progress to Slide #2 and we would see it open up properly to reveal 'sub-slides' 2.1-2.10.  Then, Slide #3 and so on:
  This is still correct when published to my desktop.  But NOW, when this same e-module runs on the LMS, the Menu goes crazy as soon as you get to Slide #2:
   ALL subsequent Slide #'s in the Menu become a derivative of "2".  And then for no reason at all it will intermittently revert back to the proper slide #'s.  This will be very frustrating to the end-users!
Why is this happening?  Again, on my desktop it's fine - only when I post the published file to the LMS do I see this..

Matrix Technical Support tested the file on SCORM Cloud and saw the same errors, therefore it's not on the LMS side.  The published files ran fine on desktop and LMS up until very recently.  Is this happening to anyone else - - what's the remedy??

Please advise.  Thank you, Brandon

4 Replies
Crystal Horn

Hi there, Brandon.  That is really weird; I'm sorry you're getting such inconsistency.  

Can you let me know if this behavior is the same across all browsers, or if you're only seeing this issue in one browser, e.g. Chrome?

Also, if you can share your project files here?  I'd like to see if I can reproduce this behavior by creating the same setup in a new course.  Thanks!

Ashley Terwilliger-Pollard

Hi Brandon,

Thanks for sharing this file. 

I took a look and saw the same thing as you were describing. It seems this is a bug we have recently found in Studio 360 as well if you are using the "Number items automatically" in the player menu settings. I was able to disable that option, and you'll note it worked normally here too (this example also includes a change I made to show your Engage interaction as only one item). 

I'll let you know here as soon as this bug is fixed - thanks for bringing it to our attention! 

This discussion is closed. You can start a new discussion or contact Articulate Support.