Help needed with Context Sensitive Help not working after upgrade from 2019 Classic to Responsive 20
We have successfully used Context Sensitive Help with the Classic version for many years. We recently started the conversion to 2020. Lacking a Classic 2020 option we selected Responsive HTML5.
Under the Classic version our web pages had anchors with this:
RH_ShowHelp(0, helpUrl + '>CSH', HH_HELP_CONTEXT, helpMapId);Where helpUrl and helpMapId were defined on every page as:
<script language="JavaScript">
var helpMapId = '160000';
var helpUrl = '/help/index.htm';
</script>Everything has worked fine since 2015.
We ran the Adobe provided mapping conversion, but it only converted about 50% of our topics but we were eventually able to get all 2200 mappings into 2020.
Based on the sheer number of pages we wanted to retain the helpMapId concept from the Classic version. It appears as though the new name is helpMapNo and helpMapId is now a character string similar to what one would think of as a key in a key\value pair, but other than the name change, helpMapNo appears to be supported in RoboHelp_CSH.js so not an issue.
Using the existing RH_ShowHelp API we got the following behavior:
The browser creates the new tab and then goes to the default page.
The address bar looks like this:
…/help/index.htm#%3Cid=160000%3E%3Ewnd%3DCSH%3E%3Enewwnd%3Dfalse&t=gettingstarted%2Fwelcome_to_our_stuff.htmWhich has the correct helpMapNo in it but goes to the default page as though index.htm could not find the correct page by the helpMapNo.
We then changed our application pages to use anchors that use the Responsive API:
RH_ShowResponsiveHelpWithMapNo('/help/index.htm', 'CSH', helpMapId);This doesn’t work either. Help has the following behavior:
The Help appears to “stall”. The browser creates the new tab, creates the empty left and right Help frames and then does nothing more. We see:
…/help/index.htm?rhcsh=1&rhwnd=CSH&rhmapno=160000In the address bar and a tremendous amount of traffic to the Tomcat server but nothing more happens in the browser. The traffic to Tomcat will continue until we close the help window.
From what we have been able to find with Google, the URL looks to be reasonable and what index.htm should be able to process correctly.
What we have validated so far:
- We have checked the mapping defined using the RoboHelp application and everything looks good.
- We have looked in the generated help/whxdata/chs.new.js file and can find the helpMapNo in the file.
- We can take what appears to be the path to the .htm file associated with the helpMapNo in the help/whxdata/chs.new.js file and can put it in the address bar … /help/pathFoundInDotJsFile and the page pages shows up … sans the complete Help frames (expected behavior).
We believe we have all the ducks in a row but are at a loss for making them quack!
Any suggestions would be appreciated.
Thanks,
Arvid
