Branching Issue
Sep 19, 2011
I have a presentation where on certain slides I have branching programmed to either go back to a particular slide or forward to a particular slide. The issue is happening with two slides — one where branching is programmed to the previous button and the other where branching is set for the forward button. In both instances, the target slide is the same slide.
Any ideas what could be causing this problem or a solution to resolve it. I'm in the final stages of finishing the program.
7 Replies
Is this happening in publish or preview?
You dont really say what is wrong, is it branching and you dont know why its brancing or it is branching to the wrong slide
Phil
It is branching to the wrong slide. In both of the slides, they are branching to same wrong slide and also in both cases, I am attempting to have them branch to the same slide.
slide 163 is programmed (forward button) to branch to 165 but instead goes to 84
slide 176 is programmed (previous button) to branch to 165 but instead goes to 84
It's happening in publish. Sorry didn't see your first question.
thats a starnge one, have you changed it in slide properties? Does it keep reverting back?
I would open the presentation.xml in the published output, in the player file and do a search for slide163 (no space) and see what the branching shows, then do the same for slide176 you can manually change the branching here but this will only affect your published files
If it keeps reverting back though, you may need articulate to help out
Thanks Phil. Your suggestion is a good fix. Will see what Articulate has to say about the issue.
R.
I spoke too soon. Interestingly enough in the xml file, slide 84 (the one that those two slides are going to) has the same slide ID as slide 165. I can't believe that should be the case. Sounds like a bug of some kind.
rob
I had a similar issue and contacted Articulate support. As you noted with your slide set, there were slides with the same slide ID. The slides had to be deleted and recreated to resolve the problem. It does appear that there is a bug of some kind.
This discussion is closed. You can start a new discussion or contact Articulate Support.