DO NOT UPDATE to v11.2

There are four of us on our Course Development team all using Lectora. Two of us did an automatic update to 11.2. I HIGHLY recommend that you do not do so until Lectora fixes something.

We use survey questions to establish the Region the user works in. The result of the survey question dictates what content is shown.

If you publish to html, there is a possibility that you will not be able to see your survey questions. This is a real issue for us since we use another Review site that our SME's are directed to to review their courses. Below is response received for Trivantis Support.

The issue you are experiencing is due to a line of code that was added for IE7 in v11.2. For some reason, this is affecting some, but not all, users regardless of the version and build of IE they are using. Attached is a revised version of the file trivantis-inline.js. Replace your existing file with this one in your published content and see if that resolves the issue for you. If it does, you can simply do the same for all the existing courses that are experiencing this issue. If you don't want to manually replace this file each time you publish out, go into the directory where you have Lectora installed, move the trivantis-inline.js file from the Support Files folder into the root directory where Lectora is installed and then place the revised trivantis-inline.js file into the Support Files folder. Then, each time you publish out, it will use the new file automatically. The reason for not simply deleting the existing trivantis-inline.js file is because when we release the next update, it looks for the modification dates on existing files. Therefore, when we release the next update, you will want to delete the revised trivantis-inline.js file and move the original one from the root directory back into the Support files folder.

When I asked if they had a time frame for a fix, they did not know. This issue is affecting only the two of us who installed the update. The two employees who have not updated are NOT experiencing this issue. Very frustrating.