Trigger Issue from S1 to S2

Definitely something weird going on... For whatever reason the value of variable slide21 seems to be "false", lower case, even though the value should be "False", with an uppercase F.  I was able to get the error layer to display by changing your condition to (ignore case), but then it only displayed after the audio had finished playing.

I would try rebuilding the slide, new variable, the whole nine yards and see if that works...

Well, at least I'm not going crazy.

I am trying to avoid having to rebuild slides, as this is in another language.

Hi Melissa,

If you still have the original Storyline 1 file (it should have created a back up when converting to Storyline2) you could revert to using that one. 

I do not have S1.

Hi Melissa,

Sorry for the confusion - I thought you meant you upgraded by accident. Also it seems the second part of my response did not go through - I looked at your file and the images you shared, but based on the images I'm not sure which slide I should be looking at? I didn't see any variables with a lower case false as Brian mentioned though. 

Slide 2.1 for the specific issue Melissa is describing in her screenshots... Note I had to add a reference for the variable on the slide so that I could see what the current value of the variable (slide21) was as well as when it was changing.

Thanks Brian for pinpointing that for me. I took a look, and saw the same thing - but setting up a brand new file in the same method worked fine (even though the variable showed as "false" on the slide when it's listed as "False" in the variable box - which leads me to believe true/false variables are not case specific to begin with). We've seen a few reports of triggers with similar conditions breaking on an upgrade to SL2 so that is an issue our team is currently investigating and I hope to have additional information to share with you soon. I'll post information here, so please ensure that you've subscribed to the thread to receive notifications via email. 

Thanks Ashley, This is what I thought as well but was really struggling to come up with another explanation other than the triggers were just not working for some reason.

It's obviously been a big issue - but not one that has impacted every user or every project, so hard to pinpoint what was causing it. The more examples of it, the better to share with our team - so this thread has been linked to the report filed. 

Thank you Ashley, I too thought it something happened in the conversion process.

Would opening a new file and importing the old file fix this? 

Hi Melissa,

I can't say for certain, but importing into a new file is a common suggestion for resolving issues with a file. It did not work for me with your file though. The current suggested workarounds are to modify the trigger to include a different condition/set up and utilize that going forward. 

Do you have any suggestions on those conditions/triggers? 

Hi Ashley,

What recommendations do you have for work around triggers??

Hi Melissa,

Sorry for the delay - I was playing around with a few things on Friday but then had to leave early. I tested using a offstage button and changing the state when the media ends and it worked, but only at the very end of the slide (which seemed odd) and that got me thinking about the slide in general as the next button wasn't active it seemed till the end of the timeline. I saw you had included the "restricted" navigation as a part of your player menu - and when I changed that, I was able to use the set up you have currently with the variables and successfully see the layer. So it wasn't an issue with the upgrade of the triggers - just that SL2 when using a restricted/locked menu navigation the user can't utilize the next button until the timeline ends. So even any triggers associated with it won't work. 

That hopefully helps - and if you're manually preventing the user from using the next button to advance by showing them the layer - there should be no worries in disabling the "restricted" navigation. 

But disabling the restricted menu allows them to then click on any slide, which we do not allow. They can only return to slides they have been to, which is why it is set as restricted.

It's odd that in SL2 when using a restricted/locked menu navigation the user can't utilize the next button until the timeline ends. So any triggers associated with it won't work, but at least I know what I am doing is working properly, that's just weird.

Hi Melissa,

If you didn't include the player menu then they wouldn't be able to navigate using that, but only with the slides navigation button. This was a change in Storyline 2 based on users feedback, as previously in SL1 setting the menu navigation a user could still quickly skip slides by using the next button. I'm sorry we weren't able to find a solution that fit for your needs, but glad we were able to determine the cause and what you were running into.