Issues with tiggers/next buttons and story progress once published

I've created a learning that works in preview mode but once I publish it, there are issues. For example the next buttons do not work and some slides show the wrong images (display image for previous unrelated slide). I checked for updates and there are none. It seems like a bug. Are there other things I can try? I don't understand why it works in preview but not when published. It is usually the other way around. 

6 Replies
Lauren Beth Peterson

Bill-

I certainly can. Where would you like me to post? I'm fairly new to using Articulate so I had a colleague try it and it worked for him but will not work for me. I showed him the issues I was having and he told me to reach out to Articulate for help. Do I need to uninstall and reinstall articulate?

Thank you so much for your help,
LB Peterson

Mark Shepherd

Hi Lauren:

As eL project issues come in all shapes and sizes, there might be a number of things that cause these kinds of problems you are having.

I run into similar issues every now and again in my Storyline Projects, and they are often caused by one or more of the following causes:

  • Too many objects/images on the slide
  • Too many objects and slide layers on the slide
  • Triggers that counteract/confuse each others' actions and/or functionality
    (Trigger Collision)
  • Overly (too-) complex design elements on the slide
  • Base Layer Objects turned ON or OFF when they should be otherwise
  • Browser/browsing Issues
  • Publishing Issues
  • LMS Issues

Preview is NOT a guarantee that things will work on your LMS. 

It is merely a starting point, so it's worth keeping this in mind when developing your eLPs, hence my suggestion about keeping graphics/design elements as simple as possible, at least at first.

Where you draw your dividing line between what works and what doesn't is often something you can only gain by trial and error and making incremental adjustments (testing experience).

The more you manage your project's content and design complexity (using it only when you need it, and in as direct a manner as possible), hopefully, the less likely you will run into issues.

Hope this helps!

-Mark

Mark Shepherd

Hi Paula:

I'm sorry to hear you are having issues with your NEXT Button. 

It could be a number of things that might have caused it to malfunction, however, experience has shown me that sometimes this may happen randomly. 

You could try relaunching or re-loading the project in your browser, as well as re-publishing, to see if that eliminates the problem.

In this case, if the above suggestions do not work, I would recommend considering building a customized button solution to eliminate the Built-In Storyline Player from your Issues List.

For this reason alone, I almost always default to this method of development for all of my projects, as I don't have time to troubleshoot AS2 issues on top of everything else.

See my response to Courtney regarding how to create customized buttons in this thread:
https://community.articulate.com/discussions/articulate-storyline/delay-progression

-Mark