Highlighted

ToC books not opening in Chrome

New Here ,
Jul 22, 2016

Copy link to clipboard

Copied

Hi all,

I am using RoboHelp 11 and RoboHelp Server 9.

Some of my ToC books are not opening, but the rest are working just fine. I have these same books on a different project, and they're opening fine. Both projects are published on the same server but in different areas. They have been working just fine up until this point.

Thank you!

Adobe Community Professional
Correct answer by Peter Grainge | Adobe Community Professional

It's going to be a few days at least before Adobe can issue a formal fix but meantime they have said I can post the fix that worked for me on the understanding that it is not fully tested and at your own risk. If you want to make the change on that basis, here's what to do.

  1.     Open the following folder <install dir>\RoboHTML\WebHelp5Ext\template_stock
  2.     Create a backup copy for the following file whthost.js
  3.     Copy the original to a folder outside of Program Files.
  4.     Open the file whthost.js in a text editor with line numbering such as Notepad++.
  5.     In line 872 (RoboHelp 2015 and 2017) or line 868 (RoboHelp 10 and 11) change the following line from
        sText = sText.replace("\n", "");
        to
        sText = sText.replace(/\n/g, "");
  6.     Save the edited file and copy it back to <install dir>\RoboHTML\WebHelp5Ext\template_stock overwriting the original

Also please note I have only tested in RoboHelp 2017. Provided you make the backup as instructed, it can be reversed.

If you do go ahead, please post how it has worked for you.


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

@petergrainge

TOPICS
WebHelp

Views

6.7K

Likes

Translate

Translate

Report

Report
This conversation has been locked.

ToC books not opening in Chrome

New Here ,
Jul 22, 2016

Copy link to clipboard

Copied

Hi all,

I am using RoboHelp 11 and RoboHelp Server 9.

Some of my ToC books are not opening, but the rest are working just fine. I have these same books on a different project, and they're opening fine. Both projects are published on the same server but in different areas. They have been working just fine up until this point.

Thank you!

Adobe Community Professional
Correct answer by Peter Grainge | Adobe Community Professional

It's going to be a few days at least before Adobe can issue a formal fix but meantime they have said I can post the fix that worked for me on the understanding that it is not fully tested and at your own risk. If you want to make the change on that basis, here's what to do.

  1.     Open the following folder <install dir>\RoboHTML\WebHelp5Ext\template_stock
  2.     Create a backup copy for the following file whthost.js
  3.     Copy the original to a folder outside of Program Files.
  4.     Open the file whthost.js in a text editor with line numbering such as Notepad++.
  5.     In line 872 (RoboHelp 2015 and 2017) or line 868 (RoboHelp 10 and 11) change the following line from
        sText = sText.replace("\n", "");
        to
        sText = sText.replace(/\n/g, "");
  6.     Save the edited file and copy it back to <install dir>\RoboHTML\WebHelp5Ext\template_stock overwriting the original

Also please note I have only tested in RoboHelp 2017. Provided you make the backup as instructed, it can be reversed.

If you do go ahead, please post how it has worked for you.


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

@petergrainge

TOPICS
WebHelp

Views

6.7K

Likes

Translate

Translate

Report

Report
Jul 22, 2016 0
121 Replies 121
Adobe Community Professional ,
Jul 22, 2016

Copy link to clipboard

Copied

Have you applied all the browser security fixes that are listed on Willam's site (https://www.wvanweelden.eu/articles/robohelp-patches-and-updates?) & regenerated your help?

Likes

Translate

Translate

Report

Report
Jul 22, 2016 0
Participant ,
Dec 14, 2017

Copy link to clipboard

Copied

One of our trainers is reporting the same issue.  TOC books are not opening in Chrome.  I don't have details on the environment yet, but I have tested using Chrome Version 62.0.3202.94 on a Windows 7 system and the books open as expected. Another user has tested the help using Chrome on a Windows 10 system, and again the books open as expected.  I'm using RH 2015 to generate the help, and my version is 12.0.4.460 (which is a higher version number than what is listed on Willam's site for RH 2015). If the books are opening in Chrome on some systems, could this still be a security fix issue?  If yes, any ideas which one(s)?  Also, if yes, and if the fixes are for an older version of RH, can I just apply them to my current RH version, or would I need to uninstall RH, install the oldest version a security fix applies to, apply the fix, install the next RH version, etc., until I have applied all fixes through RH 2015?  Thanks!

Likes

Translate

Translate

Report

Report
Dec 14, 2017 0
Participant ,
Dec 14, 2017

Copy link to clipboard

Copied

OK, I am now experiencing the same thing, as is another one of our trainers.  My version of Chrome was working fine.  They were on a newer version of Chrome.  I have now updated my version of Chrome to the latest version (currently 63.0.3239.84 (Official Build)(64-bit).  Now my TOC books are not opening either.  Anyone else experiencing the same thing?  Anyone know a resolution?  Thanks!

Likes

Translate

Translate

Report

Report
Dec 14, 2017 0
Adobe Community Professional ,
Dec 14, 2017

Copy link to clipboard

Copied

First make sure that your RH2015 has the most current patches applied. Regenerate & test again. I've got RH10 WebHelp working with that latest version # of Chrome you specify and it works - but I had to replace whform.js, whibody.htm, whphost.js, whproxy.js, whutils.js to get it working across all browsers.

Likes

Translate

Translate

Report

Report
Dec 14, 2017 0
Participant ,
Dec 14, 2017

Copy link to clipboard

Copied

I went to File > Updates.  I got the message: "Your applications are all up-to-date as checked: less than a minute ago." My version number did not change.  When you mention copying the whform.js and other files, are these files that I should be able to get from WIllam's site and then just paste into the appropriate locations for RH 2015, or would I need to install an older release add the fixes, update the release, etc.?  Thanks.

Likes

Translate

Translate

Report

Report
Dec 14, 2017 0
Adobe Community Professional ,
Dec 14, 2017

Copy link to clipboard

Copied

Old releases of RH are separate installs, so "building up" files won't work that way. You'll need to check out Willam's site and search the Forums for Chrome fixes from Adobe to download and evaluate. Always make backups of the existing files before replacing them with fix files (because you may have to restore them). I use a tool called Beyond Compare to check the insides of each (because I'm repairing such an old version of RH in production). You may end up having to move up to RH2017 to get the latest official fixes from Adobe.

Likes

Translate

Translate

Report

Report
Dec 14, 2017 0
Community Beginner ,
Dec 14, 2017

Copy link to clipboard

Copied

Hi Tim,

I can confirm: As of today, my RH 2017 webhelp output is doing the same thing - Chrome just updated, so I suspect this is the cause as I did not see this problem yesterday when I generated this project.

I also have output that I generated last year with RH 2015 (which worked fine in Chrome), but now, same thing, books in the TOC won't open. (Caveat - they open UNTIL you click on the topic, and then they stop opening. Reload gets them going again, but only until you click on the topic again.) I think something changed in Chrome that has now broken one of the RH routines.

Luckily, this is not a problem in IE11, which is what my client is using.

I doubt applying any of the patches will help, since this is a new problem.

Likes

Translate

Translate

Report

Report
Dec 14, 2017 0
LEGEND ,
Dec 14, 2017

Copy link to clipboard

Copied

Hi there

I strongly suggest that anyone experiencing this report to Adobe as a bug.

Click here to visit the bug reporting page

Cheers... Rick

Likes

Translate

Translate

Report

Report
Dec 14, 2017 0
Community Beginner ,
Dec 14, 2017

Copy link to clipboard

Copied

Reported. Note that output is still working ok in IE11 and in FF 57.

Likes

Translate

Translate

Report

Report
Dec 14, 2017 0
New Here ,
Dec 15, 2017

Copy link to clipboard

Copied

Just voted for it (same issue with RH 2015 12.0.4.460 and Chrome Version 63.0.3239.84 Official Build (64-bit).

Likes

Translate

Translate

Report

Report
Dec 15, 2017 0
Adobe Community Professional ,
Dec 15, 2017

Copy link to clipboard

Copied

The bug can be found at Tracker for anyone else finding this problem.


See www.grainge.org for RoboHelp and Authoring information

@petergrainge

www.grainge.org for free RoboHelp & Authoring info. Use the blue Reply button at the top to help me help you.
The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Dec 15, 2017 0
Participant ,
Dec 15, 2017

Copy link to clipboard

Copied

Jeanne, thanks for confirming the issue, for providing additional detail about the bug, for logging the bug report (I voted), and for letting us know this issue also applies to help files generated with RH 2017. Also, Chrome has a new official build out, Version 63.0.3239.108 (Official Build) (64-bit), but this build does not resolve the problem. Again, thanks!

Likes

Translate

Translate

Report

Report
Dec 15, 2017 0
Adobe Community Professional ,
Dec 15, 2017

Copy link to clipboard

Copied

Voted! That newest build just busted my patched up WebHelp project in the same way others are describing it. Grrr...browsers!

Likes

Translate

Translate

Report

Report
Dec 15, 2017 0
Participant ,
Dec 15, 2017

Copy link to clipboard

Copied

Not sure if it matters, but I reported the same issue using Google Chrome's Settings > Report an issue option, which is on the same page as the Chrome version info.

ChromeIssue.png

I let them know that one of our suggested workarounds is using a different browser (e.g., IE 11) until the issue is resolved.

Likes

Translate

Translate

Report

Report
Dec 15, 2017 0
New Here ,
Dec 15, 2017

Copy link to clipboard

Copied

Yeah, same here. After discovering this thread and learning the solution was outside of my own influence, I've spent the morning trying to let my internal and external audience know to either stick with using the search engine or open their hearts to Firefox.

If we voted on that bug, are we notified if something changes?

Likes

Translate

Translate

Report

Report
Dec 15, 2017 0
Adobe Community Professional ,
Dec 19, 2017

Copy link to clipboard

Copied

Re "are we notified if something changes?"

Not generally but with something like this once an update is released, it will likely be commented on in forum threads. Also you can go the Tracker bug base at any time to see its status.


See www.grainge.org for RoboHelp and Authoring information

@petergrainge

www.grainge.org for free RoboHelp & Authoring info. Use the blue Reply button at the top to help me help you.
The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Dec 19, 2017 0
Community Beginner ,
Dec 17, 2017

Copy link to clipboard

Copied

Hi all,

Turns out I do have some Chrome users in the Help audience for this project, so ...

Workaround is to turn off WebHelp Settings > Navigation > Synchronize Table of Contents, or use Preferred Format: HTML.

Reduces functionality, but at least the output is not broken in Chrome.

I will add this info to the bug report as it seems the source of the problem is the syncing of the TOC.

Jeanne

Likes

Translate

Translate

Report

Report
Dec 17, 2017 0
Adobe Community Professional ,
Dec 18, 2017

Copy link to clipboard

Copied

Changing to pure HTML. which disables synchronization, works but I'm not finding turning off synchronization alone works.


See www.grainge.org for RoboHelp and Authoring information

@petergrainge

www.grainge.org for free RoboHelp & Authoring info. Use the blue Reply button at the top to help me help you.
The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Dec 18, 2017 0
Community Beginner ,
Dec 18, 2017

Copy link to clipboard

Copied

Worked for me using Chrome 63.0.3239.108 (Official Build) (64-bit).

Likes

Translate

Translate

Report

Report
Dec 18, 2017 0
Adobe Community Professional ,
Dec 18, 2017

Copy link to clipboard

Copied

Weird as I'm on the same build. I cleared the cache as well to be sure.


See www.grainge.org for RoboHelp and Authoring information

@petergrainge

www.grainge.org for free RoboHelp & Authoring info. Use the blue Reply button at the top to help me help you.
The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Dec 18, 2017 0
New Here ,
Dec 18, 2017

Copy link to clipboard

Copied

I'm also on that build now, but it's still not working...

Likes

Translate

Translate

Report

Report
Dec 18, 2017 0
Participant ,
Dec 18, 2017

Copy link to clipboard

Copied

I got the same results Peter posted, too.

Likes

Translate

Translate

Report

Report
Dec 18, 2017 0
Explorer ,
Jan 02, 2018

Copy link to clipboard

Copied

I have now had the same issue reported to me. I am using RH 2017 and the user is viewing through Chrome version 63.0.3239.108 (64 bit).

I have added my vote and comment to the Adobe Tracker.

Chris

Likes

Translate

Translate

Report

Report
Jan 02, 2018 0
New Here ,
Jan 05, 2018

Copy link to clipboard

Copied

It looks like there was a new build on Thursday, and now I can't recreate this issue.  Maybe Google did us a solid?

Likes

Translate

Translate

Report

Report
Jan 05, 2018 0
New Here ,
Jan 05, 2018

Copy link to clipboard

Copied

Never mind.  False alarm

Likes

Translate

Translate

Report

Report
Jan 05, 2018 0
Participant ,
Jan 05, 2018

Copy link to clipboard

Copied

Interesting.  My supervisor contacted my yesterday to let me know it looked as if the issue had been resolved, but then--even before I had a chance to verify the information--he let me know it was not working again.  Anyone else have the experience of seeing the TOC books work correctly in Google Chrome in the last day or so?  Wondering if there was a recent Chrome update where it did work but then a subsequent Chrome update that broke it again. Thanks.

Likes

Translate

Translate

Report

Report
Jan 05, 2018 0
New Here ,
Jan 05, 2018

Copy link to clipboard

Copied

It appears the issue now exists only in our landing page, but not with the projects underneath, which is what threw me off initially. 

Likes

Translate

Translate

Report

Report
Jan 05, 2018 0
Adobe Community Professional ,
Jan 05, 2018

Copy link to clipboard

Copied

I just tested mine with build 63.0.3239.132 and it's sometimes opening up the "books" but then not wanting to close them, so I think it's still a bust.

Likes

Translate

Translate

Report

Report
Jan 05, 2018 0
Community Beginner ,
Jan 05, 2018

Copy link to clipboard

Copied

With TOC synching on, it will open/close books just fine as long as focus stays on the TOC. As soon as you click on the topic pane, it is broken and no books can be opened or closed. At least that is what I have seen.

Likes

Translate

Translate

Report

Report
Jan 05, 2018 0