January 2, 2019 at 3:48 pm #414610
So, I just updated from 17 to 18 and today when I went to publish my first course that was originally made in 17, and now 18, all of the buttons in it turned pink. The image buttons with custom images, removed the images and turned the background pink, the transparent images that I used also became pink in all 4 stages.
It wasn’t like that before I saved and published. Now, in my Lectora course itself (not just the published version) the buttons are all pink.
This freaks me out. What else has gotten messed up in this update?January 2, 2019 at 3:50 pm #414613
Update – the course doesn’t work anymore in ReviewLink. Fantastic.January 2, 2019 at 6:04 pm #414655
Adam CainMember14 pts@cainam
I believe I had that issue when I opened in 18, then back in 17… (Or vice versa? I can’t remember) the pink might be a selection of no color. After that happened I try not to switch editing titles between Lectora versions…January 3, 2019 at 3:55 pm #414745
Heidi StrangbergMember3 pts@heidi
When we have older courses that need to be updated, we have no choice but to change versions. My older course (2015) also showed pink buttons and changed text box backgrounds but ONLY when published to SCORM. I hope there is a fix for this?January 3, 2019 at 4:01 pm #414750
For me, the solution was going back through the course and fixing every single text, invisible, and image button manually. It also seemed to change the font/font size in the text buttons. I just hope it didn’t mess with any of the actions or variables. The jury is still out on this one…January 4, 2019 at 10:13 am #414810
Heidi StrangbergMember3 pts@heidi
Now that we have done more investigating, we think this course was accidentally opened in v17 after it was updated to v18. that caused the corruptions, because you cannot revert to previous versions.January 4, 2019 at 10:23 am #414814
Adam CainMember14 pts@cainam
That would be in line with my experience Heidi. I might add the course was opened and saved in v17 after it was saved in v18. I think I caught it one time quickly when I accidentally reopened in 17 after saving in 18 (since 17 was tagged as the default program to open the .awt file). I closed in 17 without saving, and opened back up in 18 without the issue.January 13, 2019 at 10:28 pm #415361
That seems an inappropriate (typical?) response for Lectora. That is, instead of warning you that you are attempting to open a title with a version of Lectora that is older than the one the title was last opened/saved with, Lectora corrupts it.January 14, 2019 at 10:13 am #415373
We are working on the pink button issue for the next maintenance release, as well as correcting the issue where you get the message if the title was from an older version of Lectora where we’ll save a copy of the AWT file for that version. v18.0.2January 15, 2019 at 12:33 am #415400
Perhaps some more thorough testing, before you make any future releases, is in order?January 15, 2019 at 8:34 am #415441
Just a note for any Trivantis people on here – your product is great, but it’s more than twice (sometimes 3x) the price of other industry standard eLearning software. We’re getting pressure to move to other similar, more cost effective software, so you might want to make sure that the quality of your application is a justification for the cost. Things like this may seem like trivial mistakes or misses by your dev team, but to consumers that are paying almost $10K a year in licensing fees for a team, these omissions are red flags, and may be used by the number-crunchers as justification to move to a cheaper, more polished tool.January 15, 2019 at 6:47 pm #415478
Alas, moving to a different/better product is not without it’s own downside:
– you need time to learn how to use it
– you need time to learn how to structure courses appropriately for your needs
– you need time to work out the ideal format for images, audio…
– other products have their own quirks e.g. in Captivate how do you get one advanced action to call another?
In my opinion, releasing a product early so that its paying users become the testers is the practice that they should refrain from.This post has received 1 vote up.January 16, 2019 at 10:19 am #415507
In my opinion, releasing a product early so that its paying users become the testers is the practice that they should refrain from.
That’s hard to argue with, of course. I’d add (as an old-school IT guy) that they should fully document their product, in particular the scripting interface. I am also old-school CBT: I still miss Asymetrix Toolbook, with its amazing script language that also worked in the development environment.January 16, 2019 at 10:30 pm #415540
Basically there’s 3 types of testing: unit testing (testing that individual components do what they are supposed to do); integral testing (testing that components are working together as they are supposed to do); and, operational testing (testing that the app is operating as it’s supposed to).
If the initial design was lacking then unit and integral testing are “impossible”. That only leaves operational testing. If a bug is discovered not only do you have to fix the bug, retrograde testing also needs to be done (to make sure you didn’t break something else) as well as including the test for the bug in all future testing.
Does Lectora get more that operational testing? (My guess is “no”.)February 6, 2019 at 8:38 am #416959
And now, there’s this Trojan that was found in the latest update for 18…
Hello, Thank you for contacting Trivantis Customer Solutions. We understand that you have encountered an issue with the most recent update to Microsoft Windows Defender quarantining one of Lectora’s application files, CefSubProcess.exe. This file is a valid Lectora file, and has been included since version 17.1. We are actively working with Microsoft to ensure that the file is no longer quarantined.
What the people at Lectora don’t seem to know is that the second that a Trojan is discovered on our government computers, secret IT people drop from the ceiling (minutes after the Trojans are flagged) and take our computers and immediately format them. Yes, data is normally backed up, but do you know how long it takes to backup, delete, and re-image a computer? For us, like 24 hours. And then, do you know how long it takes to reinstall all of our programs? (Adobe CC2018, Cinema4D, all the friggin plugins and addins that we need to call or email to de-register, re-register, etc…) Another full day.
Not happy with the QC at Trivantis. I’m sure they’ll blame Microsoft for this, but I’m not seeing too many other companies having these issues.
You must be logged in to reply to this topic.