We are using Saba 3.5. In general, we don't have problems with our Lectora courses. Lately we have been experiencing specific problems with Captivate files in Lectora (Saba Publisher) and the trivNextPage() function.Not all users, but users with certain computer configurations have not been able to get past the end of the Captivate file with a button calling the trivNextPage() function. We were hoping to use the JavaScript Title Manager, assuming that it was an issue with Sun Java 1.4 or something related.Our test showed that if we published the Captivate file using Flash Player 7, which is our company standard, trivNextPage() from Captivate to the Lectcora HTML pages would not work for the small group of users. If we published with Flash Player 8, it would work for those users that happen to have Flash Player 8 or later. Users that didn't have a problem originally then had problems because they did not have Flash Player 8 and do not have rights to download the latest Player.Our short term solution:We opened the Captivate file in Flash and found the button calling the trivNextPage() function had the following ActionScript.getUrl("javascript:trivNextPage()", "_self");We removed "_self" which then allowed all users go get past the button calling the next Lectora page.Importing the Captivate file into Flash then raises issues with how Flash imports the audio (Export to first frame for ActionScript and timing of audio to the timeline). Doing this does not let the preloader work as it does in Captivate. All the audio loads before the preloader animation starts...from one problem to the next.
