Script Errors in TOC from RoboHelp 9

[RHRyan]

Hello, all. I can usually find the answer to my problems by searching existing threads, but I can't seem to find a solution this time. I recently upgraded from RoboHelp 7 to 9.0.2.271. I have published WebHelp locally and then checked files in to a Team Foundation Server to be deployed to a testing environment. Locally and on the QA site, the output looks fine for me and the TOC works as expected. However, other users on Internet Explorer 7 and 8 (I have IE8) get script errors when trying to click on pages in the TOC.

I zipped my local files and dropped them on a shared drive and asked one of the users to copy them to his machine and open the start page with his browser. He still gets the script errors, whereas another user can open them locally with no problems. This makes me think the problem is not in the RoboHelp files themselves, but I am not sure.

To further complicate matters, in the staging environment, a different server from QA, the TOC and Index are empty! This is obviously a separate issue, but I am stumped. This issue occurs in IE 6, 7 and 8. It does NOT occur in IE 9 or Firefox.

Any ideas?

[RHRyan · Accepted solution]

This issue was fixed with a reply from another discussion:

Re: RH8 > WebHelp > TOC won't render in IE8 via HTTPS - Fix/workaround?

If TOC/Index/Search is not working in IE7/8/9 via HTTPS, Please try the following steps

1. Go to https://acrobat.com/#d=WqbdTq-2R79ToU08-zfBEw
2. Download IESearchIssue.zip file. Unzip it.
3. It will create a folder IESearchIssue. It has two subfolders
   1. RH8.0.2
   2. RH9.0
4. If you are using RoboHelp 8.0.2, go to RH8.0.2 folder.
5. if you are using RoboHelp 9.0, go to RH9.0 folder
6. Go to <RoboHelp Install Folder>\RoboHTML\WebHelp5Ext\template_stock folder and rename the file whutils.js  to whutils.js.bak
7. Now paste the already copied new whutils.js in same folder.
8. Now again generate webhelp output of the required project.
9. Host it to your webserver and check if it works.

[Margaret_Becker]

This link no longer works. Is there any other way to fix this problem?