Deleting Triggers

May 09, 2014

Hello! I'm having an odd problem. I need to restrict the course navigation, and I found an excellent tutorial:

//www.screenr.com/J5K8

But at the end of the video, the author says I should go through the slides after pasting the new "Jump to next slide" trigger and delete the default "Jump to next slide" trigger. He is able to do it in the video, but I can't- the delete button is grayed out for me, even though I followed these directions and there's an alternate continue trigger (the one I created and pasted).


Anyone know if there's a setting I can adjust to make it possible to delete the default trigger? If not, this "paste the custom trigger you just created" strategy won't work- I'll have to edit every single default trigger if I can't delete it.

Help! :(

5 Replies
Rachel Smith

Hi Christine,

Thanks for the idea. This doesn't fix my problem, but I already submitted it to Storyline support before thinking to post it here and got a response that has a workaround. 

----------

This is the workaround:

1) Use Story view and select slide the problematic slide.

2) Disable the Next button in the slide properties panel.

3) Re-enable the Next button.

4) Now you will be able to delete the trigger.

I'm not sure why some slides need this workaround whileother identical slides can delete the default jump to next button trigger.  Were some slides imported from another file? 

--------

My answer to the follow-up questions is "yes," most of these slides were imported. That may be the reason why this occurs- We designed the entire course in the same .story fileoriginally, but for course publication we needed the 5 distinct modules to betheir own .story file for upload (because they're separated by native LMSquizzes and other modules in their final published form). Therefore I wasadvised by the e-learning community to import each module into a new projectand save them that way. My best guess would be that any slides with deletable Nextbuttons were added as part of the individual module revision process.

Hope this makes sense to you- thanks for your help!

Christine Hendrickson

Hi Rachel!

A lot of times this can happen if the "Jump to" trigger is also tied to a slide that no longer exists, or simply wasn't imported at the same time. That might be something to watch for, especially if you're going to do this a lot with your modules. 

I'm glad to hear that our support team was able to help with deleting the triggers. 

Also, remember that you'll want to work locally with project files - including those that you import:

  • Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file corruption, loss of audio, and other unexpected behavior. 
  • You should also make sure the directory path to your project files and your published output is less than 260 characters (for example C:\Articulate).
  • Avoid using special characters, accents or symbols in your file names (this includes spaces and underscores).

Additional information regarding "Naming Files, Paths, and Namespaces" in Windows operating systems can be found in the following Microsoft article.

That will help avoid any corruption that can come from working off of external sources - if you haven't already, try to make sure all the files you work with are local. You can store them elsewhere, but try to make sure they're local if you're making any changes, or pulling content from a file into a new one.

Thanks!

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