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 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. (Note that we don't provide support for either workaround.)
As of July 10, 2024, SharePoint users will find that they are required to reenable the Custom Scripts feature every 24 hours, reverting the Custom Scripts setting to its default and disabled state. Please see Microsoft’s article on Custom Script settings for more information.
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.PowerShellRun 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 a .html extension in your unzipped published output folder to .aspx (keep the same file name). To do this, right-click the file, choose Rename, and then replace .html with .aspx. (Most projects only need to rename the analytics-frame.html and story.html files.
Finally, upload the published output to your SharePoint site, then click story.aspx to launch your Articulate course. This change should take effect immediately.
68 Replies
Hi everyone, do we know if something changed in Articulate 360 settings that would affect this process. I used to do the exact same thing as explained here to share my web published files via SharePoint (replace .html by .aspx). Now, instead of launching the file, it downloads the story.aspx document.
Hello VanessaRaby,
Thanks for reaching out!
We didn't change anything that could have affected how Articulate content is displayed in SharePoint. Note that SharePoint is proprietary software offered in the Microsoft 365 suite. It is designed to host websites created within SharePoint. This means they can release updates in their environment to improve the experience for internally created websites, which could also have an inverse effect on content created from third-party software.
Please check with your SharePoint administrator to see if the behavior you described can be changed in SharePoint's environment.
Hi,
We're running into the same problem: we want to make a Rise course with integrated storyline blocks available for clients who do not have an LMS. So we published a version for web on our secured SharePoint Online site. The Rise module loads fine, but they cannot see the storyline block. Instead, a html file is downloaded but cannot be opened of course.
So, my question is: if our admin enables this script, will it only be active for 24h? So basically, they would have to enable it every day until every client (we're talking about hunderds of people) have seen the course?Custom Scripts are not working like this (It needs to be enabled during the upload of the course, not the whole time it is online).
Storyline block is shown as an iframe within Rise course, that might be the case. Did you enable the Customs Scripts during the initial upload and you still have the issue, or you didn't enable it at all and somehow Rise course is working and only the Storyline block is not?
Cross-linking these two posts since they're now related.
ASPX Files Now Download Instead of Launching from SharePointwhy is this so complicated?
Renaming had worked for me until very recently, and it works with historical files. I just created a new file. When I upload to SP and try to link it, the link refers to "download" instead of "story" (company related information is deleted from the beginning of the link): _layouts/15/download.aspx?UniqueId=6d2f67f637f94a0da02fbdc5292ba888&e=Lz7zPL. What may cause this issue?
Any update on this? I am encountering the same issue.
Hey
So this is what my business IT infrastructure Engineer said to me...
Microsoft themselves have disabled the custom script feature on a SharePoint as a standard feature. ( he confirmed this with Microsoft). It can however be enabled for a specific site (your IT admin can do this if not you) but it will auto turn off after 24 hours.
Due to how long it take for my business to push through updates i get about 48 hours sometimes 72 before it resets.
Uploading the files itself they need to be converted to the ASPX file I also find that in the Story content folder and the Mobile folder once you have uploaded them to SharePoint you need to create the blank folders "notes" and "slides" in each as SharePoint wont upload these empty folders
Hope it helps
So my little input, as I also have 'download' problem.
First of all, you can discard entirely analytics-frame.html. If you rename it to .aspx nothing will happen, as sources INSIDE story.html refers to analytics-frame.html. If you change extension of the physical file, it won't magically replace the inside story.html reference to the new one. It will produce the same error in the console - file not found. And analytics-frame is not a necessary file to run the course.
And to the topic - I created library and uploaded files right into it. You can see it has library icon, and I have two documents libraries, which I one just created.
And yet when I click story.aspx it tries to download. And it probably will, always, unless you have some option(*) somewhere checked that @Jennifer Brown didn't include in the instruction - not her fault, as we are just learning guys, not neccessarly sharepoints superadmins ;)
I did however nailed things down a little.
1. You need admin privileges or be able to contact your sharepoint admin (and convince them to enabling option opening vulnerabilites in the sharepoint ;)).2. You need to enable Custom Script, either on the admin level (permanent solution for all sites) or site level (temporary, 24h solution for just one site/site collection). You can read here.
3. Then you should view your site (communication or teams channel, doesn't matter at all) contents and navigate to the Styles Library. Inside, you can create new folder, for example TestCourse, and upload all Storyline published files (with of course ALREADT CHANGED story.html to story.aspx, because amount of people not getting that you need to do that beforehand is astonishing) into it. If you don't enable custom script, you won't be able to upload files here at all, that's why.
4. Now when you click the story.aspx you should indeed open a fully functional storyline course. You can embed it into any other site (at least within your space).
I've managed to do that on my 'test' sharepoint and now I will try to test it organization-wide ;) If someone might have an idea about (*), I mean why it is working from document library perspective for some, and for others not, I'd happy to hear. As enabling custom script and trying to run the course from another location than Styles Library produced "download" window instead of showing course, and trying to access direct link or embedding it, produced "File not found" notification.
My org's Sharepoint admin and I are having the same issue described above - the story.aspx file downloads instead of opening, and nothing populates when you try to open after downloading. Any help would be so appreciated!
Haley, have you seen my comment, Viewing Articulate 360 Content in SharePoint Online - Articulate Storyline Discussions - E-Learning Heroes - Page 3?
If you are trying to load it to a Teams Site, those seem to not work. Even if you publish to the top level, not inside a folder, Teams SharePoint does not seem to work the same on. It works on a SharePoint Communications Site, though.
Make sure to change the file extensions locally before uploading as well.
Hi. Thanks for all of your help on this subject. I have followed every single step. Would you have any other idea or advice on why it would still not work?
The file extension was changed, all files were uploaded to a library (not in a folder) on a Comms site.
When I try opening up story.ASPX from the library it just wants to download the file. When I link to it, it tells me that something went wrong and the file is not found.
Here's most of what you need to know to publish Storyline to SharePoint.
Publishing Storyline for SharePoint
- Authoring Tools: Storyline 3, Storyline 360, likely Rise
- SharePoint: SharePoint.com “Modern and On-Premise “Classic” with ability to 1) create a library, and 2) upload files
- Operating System: Windows 10/11, with ability to edit file extensions
- Publish to Web
- Change .HTML file extensions to .ASPX
- Upload to a SharePoint Document Library
- Use the Story.ASPX file as the target file
- Verify the files will be at the top of a SharePoint library and not a folder in a library
- Ensure Storyline is up to date and save before publishing
- Ensure “clean” publishing and do not overwrite existing folders
- Must change the file extensions before uploading to SharePoint
- Publish to Web (save project first, publish clean)
- Change any .HTML file extensions to .ASPX from File Explorer window:
- If file extensions are visible, slow double click and change the HTML to ASPX.
- Alternatively, right click and select Properties and change in Properties window
- Say yes to message, “If you change a file name extension, the file might become unusable. Are you sure you want to change it?”
- Storyline web publish only has two HTML files: Story.HTML, analytics-frame.HTML
- If attempting to use Rise or publishing for xAPI, search for all .HTML files
- Deliver output folder to whomever can upload to SharePoint if you are unable to upload yourself.
Actions for SharePoint Communications Owner/Designer/Member
This will not work for a Teams site, only a communications site.
- Create a document library just for the output
- Must have it’s own library
- Best practice: no spaces in library name (Pascal_Snake_Case for example)
- Place the contents of the output folder into the new SharePoint Library
- Upload as a group to avoid breaking connections
- Do not load the folder itself into the library
- Use Story.ASPX as the target file
- Target file may vary for other products like Rise
- xAPI target file may be Story.HTML or Index_lms.HTML
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.
Unfortunately it doesn't look like this solution will work for some people based on the SharePoint configurations. It is not possible to open a converted HTML / ASPX file on 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.
Do make sure you change file extensions before upload. Doing so after uploading to SharePoint won't work.
Also doesn't work straightforwardly on Teams SharePoint.
Unfortunately I'm not able to do more research for at least a few more days but I have noticed some folks attempting this try changing the file extensions after being uploaded to SharePoint.
Before uploading, look for the HTML files and change them to ASPX.
Hi Jennifer
are you able to tell me what your aspx file is being opened with? I've spoke to my IT department and even they are having trouble getting this to work
Hoping someone can help. My company does not have an LMS and SharePoint is my only option. I have published my course as Web for Articulate Storyline.
I think I have followed all the steps but when I link to the story.aspx file it only shows a blank page and wants to download. I have my library and all the files and am using sharepoint.com.
Any ideas? This will be my first course and I really need to be able to get this one out there!
