Forum Discussion
Bug? Feedback Master Slide Show Layer trigger not working?
Hi Guys,
I'm using SL3.
I've created 2 sets of menu icons using:
- Slide Master (Blank) layer
- Feedback Master (Incorrect Feedback) layer
Showing layer in Slide Master (Blank) using triggers is working but showing layer in Feedback Master (Incorrect Feedback) is not working. Please see screenshot attached. You can also check SL3 rawfile to explain this further.
I hope you can help. Thank you in advance.
Regards,
Erwin
Hello Everyone!
I wanted to share some great news! We are no longer seeing this bug that prevented a feedback master layer from displaying when being triggered from the base layer within a Storyline course.
Please make sure that you are using the current version of Storyline 360 (3.72.29699.0). This guide walks you through installing, updating, and opening Articulate 360 apps.
Please let us know if you're still encountering the issue and we'd be happy to continue troubleshooting with you in a support case.
Thanks for checking in, Janet! We've still got our eyes on this bug. If anything changes, you'll be alerted since you're now subscribed to this discussion!
Thanks Alyssa!
And to clarify, this worked before and doesn't work now.
I thought I was going crazy yesterday. :-)
Hi - has this bug been fixed yet, my layers on quiz feedback are still not showing? Thanks.
Hi Rita,
We're still seeing the issue where layers on a Feedback Master layout will not display when triggered from the base layer. Is that what you're seeing, too?
We'll keep you posted on our progress!
Yes, that is what I am experiencing.
Rita Clark
Senior Training and Development Specialist
Community First Credit Union
Love Where You Bank
Ph 904.371.7934 * Fax 904.371.8125
clarkr@c1cufl.org * www.CommunityFirstFL.org******************************************************************************************
CONFIDENTIALITY NOTICE:
The information and all attachments contained in this electronic communication are legally privileged and confidential information, meant only for the intended recipients. If you have received this in error, please notify us immediately by return e-mail and permanently remove any copies of this message from your system. Thank you.
Hi Alyssa,
is the issue still not solved?
Thanks for the confirmation, Rita.
It looks like your email signature came through when you replied via email. You can remove that if needed by clicking ‘Edit’ beneath your response. Here’s a quick Peek video if you need help.
Hi Stefan,
No updates yet, as this is still an open issue with our team, but we'll let folks know in this discussion once we have more info to share.
Here's an inside look at how we tackle bugs when they're reported.
Hello, I am guessing there is still no movement on this issue?
Hi Nick!
I'm sorry that you ran into the bug where layers on a Feedback Master layout do not display when triggered from the base layer.
We've got it documented, but based on the limited impact, it's still an open issue for monitoring. I'll share your experience and notify you of any changes.
In the meantime, we're happy to troubleshoot your project for any viable options. If you could share the .story file, please use this private upload link.
Katie,
With the new upgrade, I also experience that the feedback master remains buggy. Specifically, changing the states of a button on a master slide, do not carry over when an associated layout is applied. This is on an existing project opened in the new update. I have not yet tried it with a completely new project, although I get the same problem if starting clean, and then inserting a question slide from an earlier project.
Image “Feedback Master” shows all button states retain a tan color.
Image “When applied” shows a new slide to which this layout has been applied. From some mysterious place, the teal color is applied to the hover and down states. This requires me to change the button states manually on every question.
The attached Test-2.story is a file created with the new version, and then a single slide from the earlier project was added. In addition to the same problem, the feedback master button states now show colors from neither the slide nor the feedback master (New Feedback Master).
Is this part of the "limited impact" known bug; and if so, will it ever being fixed? The many replies to the thread seem to indicate that the "impact" is more than limited.
Hi John!
It sounds like you're seeing an issue with the buttons states in the Feedback Layers. It looks like the states are not changing on the Layers located in Slide View. I'm seeing this on my end as well.
We have this bug logged as well as the one discussed in this thread regarding the triggers on the Feedback Master. I've added your comments to the report and shared it with our team.
Adding my name to the list of folks that would like to see this bug fixed!
Hello Everyone!
I wanted to share some great news! We are no longer seeing this bug that prevented a feedback master layer from displaying when being triggered from the base layer within a Storyline course.
Please make sure that you are using the current version of Storyline 360 (3.72.29699.0). This guide walks you through installing, updating, and opening Articulate 360 apps.
Please let us know if you're still encountering the issue and we'd be happy to continue troubleshooting with you in a support case.
I am still having this issue on some slide masters and not others. They are EXACT duplicates of each other (round 1, round 2, round 3) the triggers from the masters work b perfectly on round 1 (and several other simulations I have made), yet rounds 1 and 2, they only b work on the most recently added slide layout.
Also, I just updated the software after reading this message and ...... same issue.
Hi Jamila,
The issue related to triggers discussed in this thread has been resolved, so there's a chance that the behavior you're experiencing might be related to something else.
Would you be willing to share a copy of your project file here or in private by opening a support case so we can take a closer look at what's happening? We'll delete it when we're done testing!
