Forum Discussion
Viewing Articulate 360 Content in SharePoint Online
Enabling Custom Scripts in SharePoint Online
Custom scripts are now disabled in SharePoint Online for security reasons by default. As a result, Articulate content with the story.html file renamed...
Sadly, the fix doesn't work for me either, but thank you for sharing what worked for you Jennifer! The .aspx file only downloads and doesn't launch anything...same behavior as the .html. I just really wish Articulate hadn't disabled the ability to embed a course in an iframe using the Share link! I have a Rise "course" that isn't actually a course, it's guidelines for creating training, and I thought I'd create interactive guidelines with videos and dynamic content embedded to underscore the importance of interactivity and demonstrate microlearning, etc., but I have to either host it on our LMS, which I will not do...the guidelines shouldn't feel like I'm tracking the user's progress...or just post a pdf version of the Rise course, which defeats the whole purpose. BOO!! Sharepoint is such a common intranet platform; I really wish Articulate would work with us on a solution that would work in Sharepoint. The iframe "share" embed was such a great solution. I'm very sad Articulate took that ability away. :(
Mary, I'm sorry to hear that.
We know that SharePoint.com can run Rise content by switching the .HTML file extensions to .ASPX. This also works for Storyline 3. So the issue is not with SharePoint.com in general. Current versions, published for web, clean output folders.
So that means something else is going on to prevent playing the content. It may require working with your SharePoint Administration team, and/or your IT security team that determines what kinds of files may run on SharePoint or on websites for your organization.
Are you certain that you are using SharePoint.com and not a legacy version of SharePoint?
I ask because there are many versions of SharePoint. If you do not see SharePoint.com in your SharePoint URLs, then it's 99.9% certain that you are using an On-Premise version of SharePoint, and not SharePoint.com.
If you are using On-Premise SharePoint, it's older, and may not meet current browser standards. For Reasons best known by your SharePoint Admin team, your IT departments, your budgeting folks. It will definitely require your SharePoint Admin team and likely someone from an IT security team that needs to be contacted (possibly "perimeter security"). And in which case, you have my condolences, because it's really hard to get the assistance that you need to resolve the issues because the root causes are not straightforward, and IT teams tend to be highly specialized and don't handle fuzzy issues.
IT support for this kind of issue is not straightforward. My best recommendation is to ask your SharePoint Admin team (not site owners, but the actual admins) to look into it and to work with IT security about what files are allowed to run on your SharePoint. Make them aware of the business needs. Ask them to look at the files in the SharePoint folder so they can identify which files may be causing issues. They may need to adjust something to allow the Rise course to play. But they should be able to resolve it.
Best of luck. I do know how challenging this can all be.
