Published version does not match source file in Storyline

Hi,

I have never seen this problem before.  I have a 4 scene course.  At one point I moved two slides from scene 3 to scene 4.  In the Storyview  in Storyline that are in the correct places.  All slide triggers are currently set to next slide.

When I published for a review, those two slides move back to scene 3 where they don't belong. 

I've renamed the file,  I've pointed the previous slide directly to the slide instead of just "next slide" and when I re-published they are still wrong.

Help.  Any suggestions?

Thansk

12 Replies
Layton Fogah

Perhaps manually change where the next slide buttons point to as opposed to leaving it in the default setting.  I had that issue once and when I manually adjusted the properties of the next buttons it worked the way it was suppose to.   Thank God I had a short file because if it was a large project it could be tedious.  I hope that helps.  Without seeing the file itself it is hard to troubleshoot.

Marco Faust

I have had similar problems in various situations and have developed some work around habits.

It appears to me that there are certain editing operations that we do that somehow do not trigger the editor to declare that a slide or object is "dirty."  "Dirty" in an editing context means that the object or slide has been altered and needs to be saved in the new configuration.  I think Storyline does this to save effort in the saving process.  This also applies to rendering/publishing.

If it were my situation, I would try moving the slides to a difference scene entirely. Save it.  Close it.  Reopen it.  Move everything back to where it is supposed to be and see if that fixed the problem.

I have been very frustrated with this in SL in numerous situations, and large overt changes to things seem to often work.  

I was just now working with some videos.  I had to correct my video in the process by which I created it, but I just simply overwrote the old video with the new video.  I then went to change it out in SL and repeatedly it would keep playing the old video even after changing it.  I finally had to delete the video and re-enter it, and that finally worked.

We shouldn't have to do that, of course.

Ashley Terwilliger

Hi Karen,

First, I'd want to check that you're following along with the guidelines here:

  • Work on your local drive (your C: drive).Working on a network drive or a USB drive can cause erratic behavior, includingfile corruption, loss of audio, and other unexpected behavior. 
  • You should also make sure the directory pathto your project files and your published output is less than 260 characters(for example C:\Articulate).
  • Avoid using special characters, accents orsymbols in your file names.

Next, I'd want to take a look at your .story file and see if I can replicate the same behavior when publishing your file and testing it. 

Karen Sugalski

Hi Ashley,

I just saw your post.

to answer your questions -

yes I am working on my C drive

My work is all stored in the My Articulate Projects folder   C:\Users\Karen\Documents\My Articulate Projects\DH- Perf Mgmt\Perf Mgmt 52914.story

I haven't used any special characters in the file name. 

I did try attaching the .story file to this response but I'm getting a Error 404 Server not found message. 

Next Steps?

Glen Murdock

I've noticed the same issues on various projects I've been working on. Changing documents out in the 'Resources' section doesn't actually change them in the published version no matter how much you delete and re-publish. The work-around I've been using for that has been to just delete the PDF or Word doc straight out of the \story_content\external_files folder and then copy in the 'new' version of the file. But if I don't explicitly check - it's pretty easy to miss. Now that I know the issue is there, I ALWAYS check when swapping out those files.

As well, one of our instructional design team is having a heck of a time with moving hot spots. She'll set everything up beautifully in Storyline, but then in the published content the hot spots appear all over the slide, not where originally placed. Checking the source Storyline file shows that everything looks fine! I've advised her to submit both her Storyline and output files to the support engineers, if she hasn't deleted them.

Ashley Terwilliger

Hi Glen,

We'll definitely want to take a look at your colleagues set up. One thought though - are you using Storyline 1 or 2? Have you looked into the slide zoom or DPI settings? As those can impact where elements appear on the slide and look different than the published output. You'll want slide zoom at 100% and use the DPI setting as described here.