Hyperlink Buttons in Studio 13

Apr 23, 2014

There is a new "hyperlink" problem introduced with Presenter '13. If I hyperlink a shape and then cover that shape at any point during the slide, it inactivates the hyperlink. This worked in '09. In our '09 to '13 conversions, we now have to reconfigure many slides because the hyperlinks stop working halfway through that slide. This is true for conversions and new builds. Here is a screencast that shows the problem.


10 Replies
Christine Hendrickson

Hi Keith,

I haven't had any luck reproducing this with a button and hyperlink. Hovering over different elements, clicking on different elements (including the timeline), etc. doesn't result in any issue on my end. 

Can you please clarify on the steps you're taking to produce this issue? 

Also, are you able to share a project or slide that contains a hyperlinked button, so I can test this on my end? You're welcome to share the Articulate Package here.

I did notice that this is happening for you during preview - I'm curious, have you tested this after publishing and uploading to a server as well?


Christine Hendrickson

Hi Keith,

Thank you very much for the additional information. I see now what's happening in the screencast - it wasn't entirely clear when I first viewed it. 

So, if I understand correctly, the shape is actually appearing on-screen on its own, further down the timeline of the slide and disappearing on its own. That explains why I didn't see you actually move anything over the hyperlinked button :)

I will certainly test this on my end and let you know if I'm able to reproduce the issue. 

I'll get back to you when I have more information.

Thanks again!

Christine Hendrickson

Hi Keith and Ke,

I've been successful in reproducing this in Presenter '13 using buttons and text with hyperlinks that are covered by an object with a "Fade In" animation. 

I experienced the same issue, where hyperlinks no longer function after being covered, both while previewing and after publishing. 

Here's my published test project, just in case you'd like to take a look.

I've done some research on the subject and I don't see any previous reports of this issue. I'm going to file a report now, to our Quality Assurance team, for additional testing. If either of you are able to provide additional packages for testing, that would be appreciated. If you find any other information that may assist with testing this issue, please share. 

I'll also tie this thread to the report, so I can update you both when there's more information. 

Thank you very much for bringing this to our attention! 

Christine Hendrickson

Hi Ke Lo,

Actually, the file I shared seems to be sufficient. I've already heard some feedback from our QA team and they're able to confirm the issue. They're working on some additional testing at the moment and I'm not sure what type of time frame we're looking at for a solution or workarounds. 

However, having said that, the more information the better :) If you'd like to share a file here, I'd be more than happy to add it to the report. 

Thank you!

Christine Hendrickson

Hi Ke Lo and Keith,

Our Quality Assurance team has resolved this issue and we intend to include the fix in a free update. While I cannot specify a time frame, I did want to share the update with you. 

Once again, I want to thank you for bringing this to our attention!

Please be sure you're subscribed to this thread. We'll be sure to share any other information or announce the update's release here. 

Have a great day!


This discussion is closed. You can start a new discussion or contact Articulate Support.