Forum Discussion
Storyline 360 to SharePoint
I recently made the switch to Storyline 360. I previously had Storyline 2 and was able to publish for the web, create the .aspx file, and upload to SharePoint through Explorer.
In Storyline 360 I can not get the same results with that process. Instead, upon clicking the .aspx file on SharePoint, I receive a prompt to save the .html file. If I click save, a blank window opens. I have tried this in both Chrome and Internet Explorer 11.
Is there something I have to do differently when using 360?
- LizPisarczykCommunity Member
Hello Everyone,
I found this thread super helpful, however, since this conversation is from 2 years ago, I am wondering if these fixes no longer work. I am trying to upload a Storyline 360 story to Sharepoint by following all the instructions here. Unfortunately, my aspx file is prompted to download every time. Articulate is no longer recommending that users download the Classic story view - meaning the new Modern view does not include the Flash html paths that have been mentioned.
Does anyone have an update to this conversation with the newer options in Storyline?
Thank you in advance!
- AldinaGoncal236Community Member
Thanks Lauren,
That link takes me to a conversation with around 9 years now.. not sure if it's helpful, thanks for answering. Other links to mention that this item would/could be included on the roadmap so hoping that was any developments on that.
Thanks
Aldina
- stantonmacke029Community Member
Is there an official Articulate response to this Sharepoint ask? (If there was one already, in this thread, I didn't see it. - Can somebody please link me?)
E.g.
- Yes/No on roadmap?
- If yes, where are we on development lifecycle?
- Recommended workaround/solution
Thanks
- JohnLuttrell-43Community Member
Stanton,
As far as I know, there has not been an official Articulate response to this community request. I believe I submitted a feature request when this thread started, but will submit another one so as to bring some attention to this much-requested functionality.
If an Articulate staff member is reading this, maybe you could shad some light on this???
Thanks,
John
- BENOITGUILLOCommunity Member
And to complete what John pointed out, I think that there is a question of resource allocation that prevents the development of SL360. All the forces are thrown into the realization of an integrated elearning platform with Rise, able to compete with Moodle, Cornerstone and Co, and to seduce big firms. If you were looking to promote a complete platform, would you at the same time be looking to develop an independent tool capable of plug into any platform or ecosystem like Microsoft or Google? I do not think so.
Too bad, SL360 is really a powerful tool with so many killing potential improvments.
- JamesWallace-f7Community Member
We had the same problem (obviously) with a Studio 360 course that was deployed on SharePoint Online. I renamed "presentation_htlm5.html" to "presentation_html5.aspx", launched the course with that, and it worked fine. Unlike John's experience above, all of the Engage interactions in the Studio course worked fine, without having to re-publish them separately.
- TomFrederickCommunity Member
I creating content with Storyline 360 and just want to share it on the web. DropBox, OneDrive, and SharePoint do not seem to work. I just spent two hours painstakingly reading over comments starting three years ago. Can anyone give an update on where this functionality stands and where I can find an SOP doc on publishing to the web from Storyline 360?
- MariaCSStaff
Hi, Tom, and welcome to E-Learning Heroes! ✨
When you publish your project for the web, you need to upload it to a web server. Take a look here for some options and tutorials.
Let me know if you have additional questions.
- TonyGonzalez-c0Community Member
- JohnLuttrell-43Community Member
Hi Tony,
What I've found is that the renaming approach no longer works consistently in SharePoint. You might try the same approach, but put the published folder into OneDrive and try opening the launch.aspx file. In SharePoint, you'll see exactly what is in your screen shot. It will either open the file and show the code or it will force a download.
The issue is the .json files that Storyline includes in published projects. It's the same issue with Captivate. Both use .json files as part of the published files. Articulate has not published anything about the issue (as far as I know), but Adobe has:
https://elearning.adobe.com/2018/11/adobe-captivate-2019-vs-sharepoint-issue-real/
Try the OneDrive approach. If that doesn't work, check with the SharePoint admin to see if .json file types can be enabled on the server. Please let us know how things go!
- TonyGonzalez-c0Community Member
Thank you for your quick response, John! When I click on the launch.aspx from my OneDrive folder, the same thing happens where the file opens in Chrome, but it shows the HTML and doesn't launch the course/tool. When I click the story.html file in OneDrive it works perfectly. I have asked my IT Admin to ensure .json file types are enabled on the server (fingers crossed that this may resolve the issue) - Tony
- JohnLuttrell-43Community Member
Great! Thanks for letting us know that the html file worked in OneDrive. I'm curious if IT is able to change the .json setting and if it works. I'll stay tuned! :-)
- TonyGonzalez-c0Community Member
We finally got the .json settings adjusted and it’s still not working for us ☹.
- JamesWallace-f7Community Member
We had a lot of trouble getting courses to work in SharePoint 365 after we upgraded from SharePoint 2013. Here's what worked:
- As a site master administrator, sign in to the SharePoint admin center.
- Navigate to the Settings tab in the left-hand menu.
- Scroll to the bottom of the page and click "classic settings page".
- Scroll down to the Custom Script section.
- Make sure these two options are active:
- "Allow users to run custom scripts on personal sites"
- "Allow users to run custom scripts on self-service created sites".
The Settings page says it may take up to 24 hours for the settings change to take effect, but I've talked to others who said under certain circumstances it may actually take up to 48 hours.
After waiting, it still appeared not to work, but I discovered that only aspx files that I uploaded after the settings change would work. Ones that were already in SharePoint before the settings change would not. But if I downloaded the older aspx files, deleted the ones on SharePoint, and uploaded them again, they worked.
Also, there may be places where one of Articulate's html files launches another html file. This is especially true with Presenter. You need to edit the html renamed to aspx files and change any statements that launch other html files to aspx.
- TonyGonzalez-c0Community Member
Thank you for the insights, I'll pass this on to our SharePoint admin!
Tony