Copy link to clipboard
Copied
I am using RoboHelp 10 with the latest WebHelp fix.
I copied the files in the fix to the specified folder in the instructions, regenerated the Help, and tested my WebHelp on IE 8-11.
When viewed locally, the WebHelp output seems fine.
The Help is accessed by our users from a web server, so I put up the newly generated output on our web server and tested the output and this is what I found:
IE 8: Index and Glossary take 3-4 seconds to load, which i guess i okay.
IE 9: Index and Glossary take 3-4 second to load. Index entries are too big and use a different font.
IE 10: When you click a topic in the Search pane, you get a blank page. When you click an entry in the Index you get a blank page. After using the Index/Search and then go back to the Contents page, you get a blank page.
IE 11: Index entries are cut off
Has anyone else run into these issue? I can live with the issues on IE 8/9/11, but the blank pages on IE 10 are unacceptable. Does the fix not resolve these issues or am I doing something wrong? Why would the fix work locally but not when accessed from a web server?
Any info would be very much appreciated.
Thanks,
Mack
Interesting. When you say latest fix, which one are we talking about?
(For an overv of all fixes, see
https://www.wvanweelden.eu/articles/robohelp-patches-and-updates)
In IE10, do you see any script errors? And if you press F12 to open the
developer console, does it show any errors/warnings?
Kind regards,
Willam
Copy link to clipboard
Copied
Interesting. When you say latest fix, which one are we talking about?
(For an overv of all fixes, see
https://www.wvanweelden.eu/articles/robohelp-patches-and-updates)
In IE10, do you see any script errors? And if you press F12 to open the
developer console, does it show any errors/warnings?
Kind regards,
Willam
Copy link to clipboard
Copied
Thanks William.
I was missing one of the fixes. I installed all the fixes that you provided and it now works ok.
Thanks so much for your help.
Copy link to clipboard
Copied
Great. Just for the record: I did not create those fixes. Credit goes to Adobe. I just made an overview page of available fixes because I had trouble keeping track.