Lectora 17.0.3 (Service Pack) now available

jvalley4735
jvalley4735 Community Member Posts: 1,357
A maintenance update was applied to Lectora today to resolve a few issues. Please view the release notes for more details (http://trivantis.com/release-notes/lectora-desktop-17-0-3).  To update Lectora navigate to the File menu then go to Lectora Preferences.  From the Auto Updates tab and select the Check for Updates Now button. You can manually download and initiate the update by heading on over to the Downloads and Release Notes page found here: http://trivantis.com/service-pack-downloads/

Comments

  • mnotermans5114
    mnotermans5114 Community Member Posts: 916
    Yesterday working with 17.0.2 and all worked fine, now updated to 17.0.3 and when publishing only a blank page shows. In all browsers and when published with seamless on or off, and accessibility set on or off....
  • mnotermans5114
    mnotermans5114 Community Member Posts: 916
    Will shoot in a support ticket, cause im not sure whats happening...
  • mnotermans5114
    mnotermans5114 Community Member Posts: 916
    I do think this is a bug in 17.0.3 If anyone can confirm this, gonna shoot in a support on this too.

    I have rebuild the awt from what i had... whats in it..

    - a audio file with events.
    - a custom skin for that player

    Rebuilding it from the previously working one... well then it works again...
    But however if you make several changes on the skin for the custom audio player and replace the existing skin in the Lectora 17.0.3 file...then the page goes blank
  • dlueken
    dlueken Community Member Posts: 13
    Hi Math,

    Is there any way I can get the/a broken title and possibly the published output too?  If you have already provided that info to our support, please send me the ticket and I will synch up with them.

    I can be reached at [email protected]  I would like to look into this ASAP.
  • mnotermans5114
    mnotermans5114 Community Member Posts: 916
    Yeah, can get it to you. I got it working now anyway. I do think the issue/bug/trouble is in the custom audio skins.
    Whenever you create a custom skin for a player, and you publish/test/check that... and at some point you feel the need to adapt that skin...the css mostly offcourse...change some classes inthere... and then try to use the same name as before for you skin...you run into trouble. Either the skin doesnt get replaced, or empty pages occur. I encountered several things like that going wrong... I will clean/mockup the title im working on and get that to you.
  • mnotermans5114
    mnotermans5114 Community Member Posts: 916
    Hi Darin, mailed you but the files bounced. Might be too big for normal mail. Will use WeTransfer and resend.

    Regards,
    Math
  • dlueken
    dlueken Community Member Posts: 13
    Hey Math,

    You can upload them to https://trivantissupport.sharefile.com/r-rcfa64c395e64e6b8 if it helps.
  • mnotermans5114
    mnotermans5114 Community Member Posts: 916
    Just uploaded a working version ( somehow i got it working by rebuilding, i do think the custom player might have caused mayhem somehow ) and the version that aint working when publishing/previewing. Support asked me for it too, so i guess you will take care of that ;-) Thanks and happy egg-hunting in the weekend....

    Math
  • dlueken
    dlueken Community Member Posts: 13
    Thanks for uploading the files Math.

    I found a problem with Lectora's publishing when it encounters an action group that cannot function (ie. goto next from last page or goto previous from first).  In this case, the action buffer did not get cleared and invalid javascript would get written out.  This would cause the page not to load.  This would also explain why you could eventually get the title to work.

    I have sent the fix to this to our QA for verification and inclusion with our next maintenance release.

     
  • mnotermans5114
    mnotermans5114 Community Member Posts: 916
    Great work Darin. Thx a lot.

    Math
  • tvoss2968
    tvoss2968 Community Member Posts: 4
    I have experienced a similar issue.  I rebuilt the course, 'imported' it into  Lectora 12, and had success launching the course in our Saba LMS only after I moved the command for the "unresolved  destination" comment I received while publishing - the bottom next was the first image with an action, I moved it to the last of the inherited objects. Once I moved the command to the bottom the issue was gone and it launched fine???

    I have yet to get a Lectora 17 course to launch (not too many being submitted, I mainly use 17 for "web tool" creation).

    When I get my test courses back from our LMS group I always get a "Some Features..." error like the attached below - this is for Lectora 17 submissions only. We are investigating whether this is Lectora or Saba.