An object-trigger that is supposed to jump to the next slide doesn't work after publishing the story, and neither do the player's Next/Prev buttons. In Preview mode everything works great.
I've seen similar posts but haven't found a solution yet. Any ideas?
Would you mind sharing steps on how we can observe the behavior on our end using your project file? I tried checking it, but it was in a language I wasn't familiar with. I wanted to be sure that I was testing your file as accurately as possible so I can assist with the trigger issue.
Feel free to add a recording if you're comfortable. Here's how:
Launch Peek 360 on your computer and click New Recording.
Select the application you want to record, then choose a microphone (if you have one) when the recording window appears.
Click the red Record button and reproduce the issue.
When you're finished, click Done on the recording control bar or click the Peek 360 icon in your system tray (by the clock).
You can preview your recording, give it a name, and then click Upload to send it to your Articulate 360 account.
Windows will notify you when it's done uploading, and a link to your screencast will automatically be copied to your clipboard.
I've been working on a project with some triggers that change the state of buttons once variables on certain layers are set to 'true'.
The only problem is that when I preview the project, these buttons appear when they're supposed to and work fine, however in Review 360, the triggers work only some of the time and the buttons are not visible for some reason.
It sounds like your triggers aren't working as intended and buttons aren't visible when published to Review 360. I'd be happy to help figure out what could be causing that!
I just had a couple of clarifying questions first:
Are these problems occurring across multiple courses or just one in particular?
If you'd be willing to share a copy of the affected .story file here in the discussion or privately through a support case, I'd be happy to test it out on my end to see if I can reproduce the same behavior.
Now that you mention it, I created the project and worked on it on the company network, but I did publish it locally, but the problem seems to still be there.
It seems to only be happening for this course.
I've submitted a case privately for you to have a look. Would you personally be able to have a look at it?
Thanks for the feedback! Great call on opening a support case!
I took a look at your case and saw that my colleague Carlo has picked it up. You're in excellent hands working one on one with him! It looks like Carlo replied to your e-mail with some follow-up questions as well.
We'll continue this conversation over in your support case!
11 Replies
Hi Tahel,
I'll be glad to help out!
Would you mind sharing steps on how we can observe the behavior on our end using your project file? I tried checking it, but it was in a language I wasn't familiar with. I wanted to be sure that I was testing your file as accurately as possible so I can assist with the trigger issue.
Feel free to add a recording if you're comfortable. Here's how:
Launch Peek 360 on your computer and click New Recording.
Select the application you want to record, then choose a microphone (if you have one) when the recording window appears.
Click the red Record button and reproduce the issue.
When you're finished, click Done on the recording control bar or click the Peek 360 icon in your system tray (by the clock).
You can preview your recording, give it a name, and then click Upload to send it to your Articulate 360 account.
Windows will notify you when it's done uploading, and a link to your screencast will automatically be copied to your clipboard.
Share the link with us.
Looking forward to hearing from you!
Hi Joe!
Thanks so much for your quick reply. Plus, now I got to try the Peek, and it's lovely!
Here's peek #1: https://360.articulate.com/review/content/bb90cc03-d787-49c3-bdb5-3cff4a47a976/review
Peek #2: https://360.articulate.com/review/content/accc6147-def8-46da-acec-953e18a5ee87/review
Looking forward to hearing from you,
Tahel
I have tried your course - and you have really a problem with publish to web
I have removed all text from the two slides acivated the player menu
ONLY the first slide is published - so the next button did't work
I could fix your project
I have
- created a new scene
- copied the two slide into the new scene
- deleted scene 1
result:
https://360.articulate.com/review/content/cf43c7cc-af03-48a0-93a9-d1e7298cc5d1/review
Jürgen
Worked like a charm!
That was absolutely genius, Jürgen =D
Did you understand why only the first slide was being published? Was it just a random bug?
So glad it is solved, and so quickly too!
Joe and Jürgen -- thank you both so much. Truly a marvelous solution.
Thanks a million!
Tahel
Hi there
I've been working on a project with some triggers that change the state of buttons once variables on certain layers are set to 'true'.
The only problem is that when I preview the project, these buttons appear when they're supposed to and work fine, however in Review 360, the triggers work only some of the time and the buttons are not visible for some reason.
Can anyone help with this?
Hi Adrian!
It sounds like your triggers aren't working as intended and buttons aren't visible when published to Review 360. I'd be happy to help figure out what could be causing that!
I just had a couple of clarifying questions first:
If you'd be willing to share a copy of the affected .story file here in the discussion or privately through a support case, I'd be happy to test it out on my end to see if I can reproduce the same behavior.
Looking forward to hearing from you!
This one wasn't a bug, the file is set to only publish one slide, would be a simple fix on the publish dialogue to publish entire project.
Jurgen fix works as once you delete the specified slide it reverts back to publish all.
This post was removed by the author
Hi Steven
Thanks for the response.
Now that you mention it, I created the project and worked on it on the company network, but I did publish it locally, but the problem seems to still be there.
It seems to only be happening for this course.
I've submitted a case privately for you to have a look. Would you personally be able to have a look at it?
Thanks again.
Hi Adrian!
Thanks for the feedback! Great call on opening a support case!
I took a look at your case and saw that my colleague Carlo has picked it up. You're in excellent hands working one on one with him! It looks like Carlo replied to your e-mail with some follow-up questions as well.
We'll continue this conversation over in your support case!
Hi Steven
Thank you for your assistance! I'll let you know how I go.