I find your product infuriating and frustrating at times. I hate that I can preview a project and the variables or triggers that I have set up work in "preview" but when I publish to Review it doesn't work. I feel like I spend a bulk of my time on that issue alone. Maddening.
I use SL360 v3.36.21289.0. I finally figured it out but the time it took was ridiculous. I'm not new to SL either. My colleague in our office experiences the same issue so maybe you are just fortunate?
Hi there, Anji. Glad to hear you've got everything sorted!
If you stumble upon any other obstacles while building out your course, please let us know. Your time is important, so we want to help keep your development running smoothly. Feel free to post in E-Learning Heroes or connect with our Support team right here!
Hi Katie. Here is an example of what I'm talking about. If you open the attached SL file and go to slide 35 and preview the slide, you'll see the triggers I've set for the next button appear to work. But when I publish it to Review 360, the trigger doesn't work. Why is this?? It happens to me so often. I would blame it on user error but I've been using SL for years now and have tried real hard to perfect my skills. To me, this is a bug. FYI, the menu in the review link is free so you can go directly to slide 35.
Thank you for attaching your file! What I found in your course is there are multiple triggers for the next button on slide 35. The best way to designate when the Next button is set to normal, is by using the trigger "Change state of Next Button when the Timeline Starts on This Slide if the State of all the Ovals is equal to Visited."
Here's what that trigger looks like in the Trigger Panel:
Thank you, but my whole point is that while I was working to make the correction, when I preview the slide, it would work. But the minute I publish it, it didn't. I eventually figured out my mistake but what I'm saying is, it's frustrating when I'm working and previewing and things seem fine but then when I publish and test, it's broken. See what I'm trying to say?
If you are previewing a single slide, the environment may be entirely different than when the entire project plays. Unfortunately, the only way to be sure how a slide will act when published is to preview the entire project. That way, when you arrive at the slide in question, you are approaching everything the way the user will. But if you preview only a single slide, there is no guarantee that that is the case. Variables and conditions may differ.
8 Replies
Hi Anji
I use variables all the time and I haven't come across this issue. Which version/update of SL are you using?
Can you share the file and maybe someone can help you.
I use SL360 v3.36.21289.0. I finally figured it out but the time it took was ridiculous. I'm not new to SL either. My colleague in our office experiences the same issue so maybe you are just fortunate?
Hi there, Anji. Glad to hear you've got everything sorted!
If you stumble upon any other obstacles while building out your course, please let us know. Your time is important, so we want to help keep your development running smoothly. Feel free to post in E-Learning Heroes or connect with our Support team right here!
Hi Katie. Here is an example of what I'm talking about. If you open the attached SL file and go to slide 35 and preview the slide, you'll see the triggers I've set for the next button appear to work. But when I publish it to Review 360, the trigger doesn't work. Why is this?? It happens to me so often. I would blame it on user error but I've been using SL for years now and have tried real hard to perfect my skills. To me, this is a bug. FYI, the menu in the review link is free so you can go directly to slide 35.
https://360.articulate.com/review/content/80a58c48-4b95-4d83-890c-38fb2b2acbdb/review
Hello Anji!
Thank you for attaching your file! What I found in your course is there are multiple triggers for the next button on slide 35. The best way to designate when the Next button is set to normal, is by using the trigger "Change state of Next Button when the Timeline Starts on This Slide if the State of all the Ovals is equal to Visited."
Here's what that trigger looks like in the Trigger Panel:
Here's the review link for you to test:
A School Nurse's Guide to Bleeding Disorders: Hemophilia
I've also attached the updated course to this discussion.
Thank you, but my whole point is that while I was working to make the correction, when I preview the slide, it would work. But the minute I publish it, it didn't. I eventually figured out my mistake but what I'm saying is, it's frustrating when I'm working and previewing and things seem fine but then when I publish and test, it's broken. See what I'm trying to say?
If you are previewing a single slide, the environment may be entirely different than when the entire project plays. Unfortunately, the only way to be sure how a slide will act when published is to preview the entire project. That way, when you arrive at the slide in question, you are approaching everything the way the user will. But if you preview only a single slide, there is no guarantee that that is the case. Variables and conditions may differ.
That does make sense. Thank you!
This discussion is closed. You can start a new discussion or contact Articulate Support.