Why are there brackets in File names for some web objects?

Hi Joseph,

Thanks for reaching out here, although I'm not sure I entirely understand your question. You may want to look at posting the sample file here, or clarifying if you've made changes within the original .story file or the published output that is causing the behavior. I'm unable to assist with any modifications to the published output but perhaps the community would be able to weigh in here if that is where the changes occurred. 

It wouldn't be much of a mystery if I made the changes to the published files. To express it in a less narrative format:

1. I created a storyline file with web objects.
2. I published the file
3. When I looked at the output, there was a .jpg file that had brackets in the filename.

Other things I know:

1. This same file was published out of storyline over a year ago, and that output does not have the .jpg file with the brackets in the file name
2. There are multiple web objects in the storyline file, but only one offending file in the published output
3. There was another instance where we ended up with these .jpg files in published content. In that instance, there was one such file for ever web object in the storyline file

Thus, I'm unsure if it's actually web object related or not.

I can try to recreate in a separate file tomorrow and post that, but I can't upload the one I'm currently working on (company confidential).

Joseph,

I can verify that I have seen this same issue a number of times with web objects. It "seems" like this jpg is the gray image that displays on the slide where you have the web object.
The images attached show the file name given by SL to the published file and what that published jpg actually is. This image never appears in the published out

Thanks Joseph for the clarification - and Brett for the images as well. It seems that the brackets are connected to the overall height/width associated with your web object and the grey image does seem to be the web object placeholder set up. Are the additional jpegs or the brackets causing issues when uploading? I haven't run into issues with them myself previously, but if so we can certainly investigate a bit further. 

SharePoint does not like the brackets and throws an error when you try to upload the files. I generally delete them and in many cases (most?) there is no problem; the course plays fine. This is an issue we've had since the upgrade to SL2; we never had the problem, as I recall, with SL1. Our LMS doesn't have a problem with the brackets and everything works just fine there.

Just an update: One of my team just had this issue just this afternoon. When she removed the offending files the course would not launch, just a blank white screen. So deleting these files is not a solution but "may" work in some instances. Again, this is just using SharePoint, not a problem with the LMS.

Thanks Brett for continuing to share that information. Editing the published output or removing files is not something we'd recommend, but as you mentioned it may work for some users. 

I found the source in my source file - it's an engage interaction.

One condition that I forgot to state at the start is that I'm publishing for web.

The conversation around which objects are spawning the questionable file names is interesting, but what is still missing is the answer to my last question, which is 'why?' Even a year ago, publishing this same file from SL2 didn't result in these file names with brackets and equal signs. Why is this happening now? Is this best reported as a 'bug' or as an 'enhancement' request to get the web output to not generate these file names?

As mentioned by others, this results in poor interactions with SharePoint. We do not have an LMS to load these into in my part of the company where I work, everything needs to launch from SharePoint.

Hi Joseph,

I don't have an answer to the why question - but it was reported to our QA team to investigate further. I do see as a part of that report that other users shared removing the brackets or renaming the file in the published output allowed it to work successfully in Sharepoint. 

Has this been resolved?

Hello Yenn - I see that the reported issue is still open with our team.

The workaround:

Renaming or deleting the image with the "{". "}" on the filename that gets created when publishing

Are you using Storyline 2 as well? Looks like this thread is linked to the report.

I wanted to share some information on how we define bugs and how we tackle them when they occur.