Skip to main content
deniseh47762385
deniseh47762385
Known Participant
September 20, 2022
Question

TOC not opening to the selected topic

  • September 20, 2022
  • 42 replies
  • 6379 views

We have a RoboHelp 2020 help project posted on our website. We have links to topics in the help project from other places on our website. For the URL in the link, we use the URL displayed in the address bar when the desired help topic is displayed, such as:

http://hsv.ternion.com/Documentation/flames21.0/WebHelp/flames/index.htm#t=SAS%2FCreating_a_User.htm

(Note that Creating_a_User.htm is in a folder named SAS.)

This works. The correct topic is opened in our help project when the link is selected. However, the TOC of our help project is not expanding to the proper place (to the entry associated with SAS/Creating_a_User.htm). Instead, the TOC is opening to some random place not associated with the topic.

Has anyone else experienced this issue, and do you know how to fix it?

This topic has been closed for replies.

42 replies

Show previous replies
Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
September 21, 2022

Does the locally generated help have the same problem? If it does not, that rather confirms @Amebr's answer.

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

 

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
deniseh47762385
deniseh47762385Author
Known Participant
September 21, 2022

Yes, the locally generated help has the same problem.

A
Community Expert
AmebrCommunity Expert
Community Expert
September 20, 2022

I have seen the table of contents to be very wrong (not specifically your issue though) because the server has cached the javascript files used to build the table of contents. When you see the issue, try clearing your browser cache, closing all browser windows ,waiting for 5min and then retrying.  If that fixes it you could ask your server administrator to set the caching (maxage) on the whxdata folder to a much smaller number or disable

 

 

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices