Viewing Articulate 360 Content in SharePoint Online
May 20, 2022
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 to story.aspx in the published output that previously worked with SharePoint Online might not work anymore.
If you don't need to track learners' progress or results, check out these free or low-cost options for web hosting.
If you need to use SharePoint Online, your SharePoint admin may be able to resolve this issue by following the steps below, depending on whether or not you need access immediately. (Note that we don't provide support for either workaround.)
Enabling Custom Script via the SharePoint Admin Center
If you don't need instant access, follow these steps.
- Go to the SharePoint admin center and sign in with your credentials.
- In the sidebar to the left of the page, click Settings. (If you're using the Modern admin center, click the classic settings page hyperlink at the bottom of the Settings page.)
- Scroll to the Custom Script section, then select the options to Allow users to run custom script on personal sites and Allow users to run custom script on self-service created sites.
- Click OK to save your changes. Note that this change may take up to 24 hours to appear.
Enabling Custom Script in SharePoint Online via PowerShell
For instant access, follow these steps.
- Open Windows PowerShell with admin privileges, then run Install-Module -Name PnP.PowerShell
- Run this command: Connect-PnPOnline -Url <url> -PnPManagementShell (replace <url> with your SharePoint URL, which will then generate a code for you to insert in your SharePoint admin center.)
- Run these commands in PowerShell: (replace the URL after -Url in the first command with the link to your static site collection, such as https://companyabc.sharepoint.com/sites/StaticSite).
(If you need help creating a SharePoint site, refer to this article from Microsoft.)
- Connect-PnPOnline -Url https://yourorg.sharepoint.com/sites/StaticSite
- $site = Get-PnPSite
- Set-PnPSite -Identity $site.URL -NoScriptSite $false
Your SharePoint site is almost ready to host HTML files! We just need to prepare the Articulate published output for upload. Here's how.
- In SharePoint, choose where you will locate this project. You can create a new folder or use the Documents location created by default with all SharePoint sites.
- Rename all the files with an .html extension in your unzipped published output folder to .aspx (keep the same file name). To do this, right-click the file and choose Rename and then replace .html with .aspx. (Most projects only need to have both the analytics-frame.html and story.html files renamed.)
- Upload the published output to your SharePoint site, then click story.aspx to launch your Articulate course. This change should take effect immediately.
55 Replies
On your local computer, after published, change the file extensions. It has to be done before uploading to SharePoint, on your local system.
I use Windows, so if you use another operating system, how you do that may vary. I don't have to use any special applications do to it; just windows explorer to get to the files and change .HTML extensions, and launch in a browser (we use chromium based browsers, Edge or Chrome).
to add to this, most people don't have extensions enabled and won't see it. While in Windows Explorer, you should have a View tab, and then there should be a checkbox for File name extensions. make sure that is checked, and then you will see the .html extension. You can right click on the filename and click Rename.
To clarify, while some organizations may restrict file extension changes, users who develop with Storyline should be able to change file explorer settings to view file extensions and to edit them. But that is something that goes beyond the question. If you cannot view or edit file extensions, then whoever can upload to SharePoint must make sure the file extension changes are done prior to uploading to SharePoint.
I Was having the same issue after following all the steps listed. I have figured out how to make this work. Happy to share how though not sure if people can see my responses as no one answered my initial query
Hi Hayley. Yes please share if you can get this to work. I believe it has to do with changing the settings in SharePoint to open modified aspx files. But please share however you got it to work.
Here's most of what you need to know to publish Storyline to SharePoint.
Publishing Storyline for SharePoint
High Level Steps
Before You Begin
Actions for Storyline Author
Actions for SharePoint Communications Owner/Designer/Member
This will not work for a Teams site, only a communications site.
Important Considerations
How organizations manage computers images, permissions, cloud backup/storage, and SharePoint can vary far beyond what can be covered here. Contact your support teams for assistance if you have any issues at any point.
This works for a SharePoint Communications site, what most people think of as SharePoint, and not a Teams site. When testing on a Teams site, even opening up "in SharePoint" and getting to the Site Content level, creating a new library to put it in, it still won't work. It will only download the Story file, and not launch. My SharePoint Admin team, that manages our tenants and works with Microsoft directly, reached out to me to research this. We're not sure precisely why, even when we create a library, not a folder. For this to work, the Storyline output must be on a communications site, and output files must be uploaded into a Library, not in a folder.
We just got a new version and update for Teams in our organization (March 2024) and I attempted again to get web published Storyline output to work, and it still fails.
SharePoint.com generally sets up three SharePoint groups with new sites: Owners, Members, Visitors. Owners can create libraries (lists, etc.). Members can usually add, edit, delete items in the libraries, etc. Visitors can read. Everything SharePoint is highly configurable from the tenant level down to the hubs and sites, so exactly how this works in your organization may vary. But generally an Owner will create the library, and they or Members will add the files.
If a file downloads instead of running the WBT, then you are likely launching from a folder or a team site.
If you are still using Classic SharePoint, there may be other factors that are causing issues. Because SharePoint is so highly configurable, there are may places where things can create headaches.
Publish to web only; the output has less files and doesn't include the required files to send data elsewhere. This can impact whether or not it will work on your particular SharePoint tenant. Publishing for an LMS includes more files and ones that send data. If you opt to use an LMS publishing option, note there will be more HTML files that will need to have their extensions changed.
Files cannot to be ZIP'd up on SharePoint for this to work.
Storyline 360 has an option to publish to video which means a single file and may be a suitable option.
Windows File Explorer settings and what's available to you varies, depending on Windows version, edition, and your organization's settings/policies, etc. The variations are beyond scope of these steps, so you may need to consult with your IT support.
Changing file extensions should only be done when you know exactly what you're doing and why. So don't do this for fun for other circumstances. These are specific steps for specific circumstances and are known to work for using Storyline on SharePoint when published to web. Changing file extensions changes the default program to open it.
The file extensions must be changed prior to uploading to SharePoint.
Cloud backups and other settings may cause issues when trying to change; again, contact your support team for assistance.
General Best Practices and Steps to Save You Headaches
Always ensure latest version. Storyline 3.20 still works as of the date of this comment. If using S360 or any authoring tool, always use the latest version to ensure it works with current browser technology. What files get published, how they are structured, and where they go can change over time.
Always Publish Clean. I can't stress this enough; overwriting an output folder only updates the files that it's set to publish. Any other files remain, and they may include obsolete tech or cause issues with your output in general.
Restart your system if not daily, every other day. In the age of cloud storage, federation, and other single sign-on options, this can impact what you do as a Storyline user and as a SharePoint Admin.
Reset your browser. Both Edge and Chrome are Chromium based so they are similar. This is the new "clear cache" and "allow popups" for those of us who've been around longer than Storyline. It can resolve a wide range of seemingly random issues.
Ensure Browser(s) are current version. Just like Storyline, outdated browsers can impact the things associated with it.
All of these can not only help avoid issues, it helps with troubleshooting and isolating root causes of issues. For example, I spent a year trying to identify causes of issues with migrating an LMS from IE11 to Edge and the root cause was Storyline build versions were not verified, and the output folders had a lot of obsolete files that were blocked. It took going into hundreds of Storyline modules on our LMS to look at all the output to discover this after working with multiple teams including Articulate (thanks, Taylor, I still remember all your help).
About Me
Currently an LMS Admin and SharePoint Site Collection Owner. I've worked with Articulate Products since Articulate was a premium add-in for PowerPoint. My background includes system administration, technical support, technical documentation, Instructional design and Instructional development. I'm often a person pulled in when folks are experiencing the sticky issues. The SharePoint Administrators in my organization use me as a Subject Matter Expert for publishing this kind of content to SharePoint.