My old YouTube videos work fine with the embed code but my newer ones (May 2015) are showing a screen that reads www.youtube.com/devicesupport. Going to this address, you'll find a message "Certain older YouTube apps will no longer be supported after April 2015".
I'm hoping other storyline creators can confirm this issue and we can find out from Articulate whether there is a simple fix to get the embedded code working again.
Thanks for reaching out here. This is an issue a few other users have brought to our attention as well here and here and that later post has a lot of great information about how YouTube has changed their code so that's something our QA team is looking into in terms of how that impacts Articulate courses.
We've researched this topic further and reached the following conclusions:
Utilizing web objects is the proper approach to add a YouTube video because it is supported in all output types. More details on that process can be found in this article for Storyline and this article for Presenter. Please note the various optional parameters you can set to tune how the video functions within your course.
As noted elsewhere in this thread, YouTube videos in projects published prior to Google's API change are NOT impacted. Therefore no action is necessary for that content to function properly.
Google is not going to reverse their actions so we are going to stop advocating for that approach.
For those of you who must use the embed code option, we did find a workaround. It requires a few steps and isn't an officially supported approach but nonetheless I thought I'd share.
You'll need to ensure that the video is properly sized prior to grabbing the embed code from YouTube as it can't be resized on the stage within Storyline or Studio.
Thanks for reaching out here, and it wasn't an officially supported method, so I don't know that it works in the latest update of Storyline 2 Update 7 (as this post was dated about 9 months ago). You'll want to ensure you're following the steps here to utilized YouTube videos, and if you're inserting them as a web object please also check out the reason here why web objects may not work as expected.
7 Replies
Hi Chris,
Thanks for reaching out here. This is an issue a few other users have brought to our attention as well here and here and that later post has a lot of great information about how YouTube has changed their code so that's something our QA team is looking into in terms of how that impacts Articulate courses.
Thanks for the update.
No problem Chris - we'll keep you posted.
Hi Chris,
Just an update, our team is aware of this and has documented it here with some potential solutions.
An update from Brian Gil, in this thread regarding the YouTube issue:
We've researched this topic further and reached the following conclusions:
For those of you who must use the embed code option, we did find a workaround. It requires a few steps and isn't an officially supported approach but nonetheless I thought I'd share.
Steps:
<iframe width="560" height="315" src="https://www.youtube.com/embed/TrcT7sseLZI" frameborder="0" allowfullscreen></iframe>
<iframe width="560" height="315" src="http://tinyurl.com/p9gm4d5" frameborder="0" allowfullscreen></iframe>
You'll need to ensure that the video is properly sized prior to grabbing the embed code from YouTube as it can't be resized on the stage within Storyline or Studio.
I used Ashley's instructions on all my videos and they all seem to work except one. Any idea why?
my embed code is: <iframe width="560" height="315" src="https://www.youtube.com/embed/P6doLJPqbjM?rel=0" frameborder="0" allowfullscreen></iframe>
my tiny URL is: http://tinyurl.com/z2hf5lv
I get the attached error each time I insert it.
Hi Holly,
Thanks for reaching out here, and it wasn't an officially supported method, so I don't know that it works in the latest update of Storyline 2 Update 7 (as this post was dated about 9 months ago). You'll want to ensure you're following the steps here to utilized YouTube videos, and if you're inserting them as a web object please also check out the reason here why web objects may not work as expected.
This discussion is closed. You can start a new discussion or contact Articulate Support.