Skip to main content
Inspiring
January 26, 2018
Answered

WebHelp does not run in any browser

  • January 26, 2018
  • 1 reply
  • 1452 views

I am running Tech Comm Suite 2017 on a Windows 10 machine. To generate WebHelp, I am using RH (within Tech Comm Suite 2017). The default browser for my company is Chrome.  In Chrome (v. 63.x), the default topic opened but the TOC was unresponsive. The WebHelp properly ran in Firefox and IE11.

I had done some research on the Adobe Forums and found an edit to the whthost.js file that Peter Grainge suggested (with the blessing of Adobe). See ToC books not opening in Chrome . I made that change but to no avail. I also looked at this forum item, Re: ToC books not opening in Chrome . I don't know whether any of my files are corrupted.

I found an update to TCS so I ran that. When I again generated the WebHelp, the tab flickered and the main window remained blank in not just Chrome but also Firefox and IE11.

I copied the output into a folder at C:\a_RH_Projects_Output in case the path was too long for the browsers to cope with. Now, the WebHelp again properly runs in IE11 and Firefox but the books still do not open in Chrome.

Does anyone have a solution to the Chrome problem? I really need for this to run in Chrome.

Thank you for any help you can offer.

Lore Eargle

This topic has been closed for replies.
Correct answer writer0101

It bounced because you didn't follow the instructions.

I see the problem in what you generated but it works fine when I generate it.

I suggest you uninstall and reinstall.


See www.grainge.org for free RoboHelp and Authoring information.

@petergrainge


Thank you, Peter Grainge, for your patience and solutions. My WebHelp now opens in Chrome as well as IE11 and Firefox. This is what I did:

  1. I uninstalled and reinstalled TCS 2017.
  2. I applied the update, 2017 Release of RoboHelp (Update 2) – Adobe Technical Communication Blog .
  3. I changed the line in whthost.js per Peter's instructions (Using RoboHelp 2017 ).

1 reply

Peter Grainge
Community Expert
Community Expert
January 26, 2018

Try generating it to a folder with a shorter path rather than just copying

it there.

More likely though is the update reversed the edit you made.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Inspiring
January 26, 2018

Thanks, Peter. I've done that and had the same result.

I also tried copying everything to Drive because one person wrote somewhere that he had success when he copied the content (or maybe generated) to a web server. From Drive, Chrome displays the HTML code rather than rendering the page.

Inspiring
January 26, 2018

BTW: The edit I made didn't fix the problem before I ran the update.