I used WebObject element into my screen by using the local path
then after publishing, we will get a folder called "WebObjects" but recently when I try to publish in LMS HTML5 Output there is no folder called "WebObjects" name. How to get this folder? Is there any alternative solution to get this folder?
I'd love to investigate what's happening within the published package! Here are my troubleshooting steps:
I embedded local web content into a slide running Storyline 360, Update 37.
Then, I published that slide for LMS with the HTML5-only (Modern Player) and SCORM 1.2 standard options selected.
From there, I unzipped the LMS package and clicked on story_content to access the WebObjects folder.
It looks like you went through the same process, so I have a few quick questions to help us determine the next steps: What version of Storyline are you using? Is this happening with other published packages or just this one?
We don't recommend changing the files in the published output since they are perfectly crafted for either the Web or an LMS. The user.js file should be home to all the Javascript that you've included in any "Execute JavaScript" triggers. Any alterations to JavaScript should be made in the Storyline file rather than in user.js.
If the values are being reset, then it must be a change in the coding. Javascript is not my expertise, so I'll leave this for our community to offer tips and tricks for JavaScript!
Tested: This will create a WebOjects folder (with needed assets for self contained output) under the story_content folder... "You need to create separate folders for source files first"
Place your Storyline file in it's "OWN" folder!
Place your html, images, etc. in their "OWN" folder!
Open storyline -- insert Web Object
At the enter web address popup -- Click the folder icon and navigate the SEPERATE folder you created for html and images
Choose the "Select Folder" button.
Publish for LMS "it should create a WebOjects folder with the assets needed to view anywhere!
7 Replies
Greetings, Eswarkumar!
I'd love to investigate what's happening within the published package! Here are my troubleshooting steps:
From there, I unzipped the LMS package and clicked on story_content to access the WebObjects folder.
It looks like you went through the same process, so I have a few quick questions to help us determine the next steps: What version of Storyline are you using? Is this happening with other published packages or just this one?
This post was removed by the author
Thank you for your replay.
I will update my storyline and check once.
I have few issues with WebObjects.
I am not able access user.js variables from webobjects.
If I add user.js in webojects, variable's values are getting reset.
This post was removed by the author
Hi Vasanth!
We don't recommend changing the files in the published output since they are perfectly crafted for either the Web or an LMS. The user.js file should be home to all the Javascript that you've included in any "Execute JavaScript" triggers. Any alterations to JavaScript should be made in the Storyline file rather than in user.js.
If the values are being reset, then it must be a change in the coding. Javascript is not my expertise, so I'll leave this for our community to offer tips and tricks for JavaScript!
I am not seeing the webobjects folder either. I am currently on Build 3.52.25156.0
Hello Melissa!
The web objects folder isn't included in the published output folder anymore. It's now linked within the index.html file.