When I publish the module not given web object folder.

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?

Old Now

4 Replies

Katie Riggio
Staff

11 months ago02/26/20 at 3:32 pm (UTC)

Greetings, Eswarkumar!

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?

vasanth kumar

11 months ago03/03/20 at 7:41 am (UTC)

This post was removed by the author

11 months ago03/03/20 at 8:04 am (UTC)

Thank you for your replay.

I will update my storyline and check once.

11 months ago03/03/20 at 11:27 am (UTC)

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.

11 months ago03/03/20 at 11:35 am (UTC)

This post was removed by the author

Lauren Connelly
Staff

11 months ago03/03/20 at 1:18 pm (UTC)

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!