Forum Discussion
Storyline links are being marked/colored as visited when not visited previously
There's a problem with the Oct 3 2023 version and later versions of Storyline. As of the 13 Dec 2023 version, this is still a problem. Using the Oct 3 and Dec 23 versions when I publish a course I see that links to triggers to show a slide layer are marked as visited when they actually weren't.
Here's the scenario: I have links on multiple slides that show layers named "modal 1", modal 2", etc. When progressing through the course and having clicked on links on one slide, the links on a following slide are incorrectly marked as visited (showing the visited state of the hyperlink). This is not good.
I see what's happening and it seems easy enough to fix.
Previously, the <a> tags for each trigger/link had a prefix in the href part of the tag for each link, like this:
And that prefix came from the ID of the text box:
Now, the href part of the link is just the ID of the link itself without the prefix, and the link is not unique enough for the browser to color it as a non-visited link:
But the ID of the text box is still there to use:
I’ve tried editing the name of the layers, but nothing I can do will resolve this.
I submitted a bug report for this, Case #03920235. Can this issue get some traction, please?
Hello, everyone! 👋
I wanted to share that we've released Storyline 360 (Build 3.84.31647.0) which includes the fix for the bug where hyperlink states didn't work as expected when navigating only with a keyboard or after duplicating a slide.
All you need to do is update Storyline 360 in your Articulate 360 desktop app!
If you run into any issues, don't hesitate to reach out to our team by submitting a support case.
Have a great day and happy developing!
Currently reverted to Release 79 to avert this issue. Please advise when resolved.
Hi Tom!
I'm sorry to hear you've also been affected by this issue!
I've included your feedback in the bug report we are currently tracking so you can be notified as soon as we have updates to share. I can confirm that downgrading your Storyline 360 installation to version 3.79.30921.0 is a valid workaround.
Sorry if this has been slowing you down!
Hi Bill!
Sorry to hear that you've run into this issue!
I see that you previously connected with my teammate Cleober through a support case. As he shared with you, our development team is tracking a known bug that causes:
- Hyperlink visited state propagates across duplicate slides.
I've linked this discussion to the bug report so you can be notified as soon as a fix is in place. In the meantime, as a workaround, we suggest downgrading your Storyline 360 installation to version 3.79.30921.0 where this bug is not observed.
Thank you for your patience and I'm sorry if this has been slowing you down!
Hi Steven,
I have also encountered this same issue. Can I also please be notified of any updates/fixes.
Thanks to Bill for posting this.
Thanks,
Linda
Hi Linda!
So sorry to hear you've also been affected by this issue!
Yes, absolutely! I've included you in the bug report which is linked to this discussion. We'll be sure to notify you as soon as we have a resolution.
Thank you for your patience!
Thanks, Steven! Hope they'll be a solution soon - we have many hyperlinks through-out our course. Holding off from reverting back to the older version (noted above) for now.
Hello Articulate staff! Happy New Year!
Any idea when the new version will be released?
Hi Bill!
Happy New Year! 🎉Thanks for following up on this.
I cannot give a timeline on the release of the next Storyline version, but based on the version history, new updates are released on a 2 to 4-week cadence. Between December and January, it may take longer due to the holidays.
We'll surely let you know here when the hyperlink bug is fixed. Stay tuned!
Thanks for the update, Eric. My deadline is fast approaching and will need to test my final course in the LMS soon. Do you know if the fix is planned for the next release (potentially this month)?
If it's not planned for the next release, then it doesn't make sense for me to wait for it so knowing that would be helpful.
Of course, it is always uncomfortable downgrading versions as you don't want to affect something else unexpectedly.
Thanks for any info you can provide.
Hi Linda!
Happy to jump in here!
The fix for the bug (Hyperlink visited state propagates across duplicate slides) is something our development team is currently working on. Unfortunately, I can't share an exact release date. Since you're subscribed to this discussion, you'll be notified as soon as we have news to share!
Hello,
Can you please add me to the list for when this is fixed.
ThanksHi Debrah!
Sorry to hear you've been affected by this issue as well!
I've included your voice in the bug report being tracked so you can be notified as soon as a fix is in place! In the meantime, here's a deeper look at how we tackle bugs.
Thank you for your patience. Sorry if this has been slowing you down!
Hello, everyone! 👋
I wanted to share that we've released Storyline 360 (Build 3.84.31647.0) which includes the fix for the bug where hyperlink states didn't work as expected when navigating only with a keyboard or after duplicating a slide.
All you need to do is update Storyline 360 in your Articulate 360 desktop app!
If you run into any issues, don't hesitate to reach out to our team by submitting a support case.
Have a great day and happy developing!
Nope! You didn't fix the issue. I just updated, published my course, navigated to a page with four links, clicked on all four, navigated to another page with 6 links and 4 of them are already marked as visited. So frustrating!! Great QA job guys!
As a follow up on this issue, I was able to verify that if I delete the hyperlink (right-click on it and choose Remove Hyperlink), and then recreate it, that the subsequent links on following slides will not be marked as visited. However, with a 150-200 slide course with dozens of hyperlinks, this is quite frustrating and time consuming to edit each and every link. So now if I have to republish a previous course because the writers found a typo, I now have to recreate every link due to this bug.
Hello Bill!
I just wanted to let you know I've responded to your reply in this discussion.
