Using RoboHelp 2015 (126.96.36.1998), and seeing this issue in both IE and Chrome. When I generate and view my WebHelp output locally, its Search feature works fine. However, when it's checked into Microsoft Visual Studio (TFS) and then deployed to a website, the Search feature might work once or twice, but on the 2nd or 3rd search, the search progress bar shows 100%, but no results appear and the page crashes.
Seems similar to the issue reported for RH9 in the discussion linked below, but I'm using a much later version of RH, and I'm not sure the RH9 fix applies. Anyone know what's going on?
Do you see any error in Chrome console when the search gets stuck at 100%.
To check, initiate a search and then open the console by pressing Ctrl + Shift + J (Windows) or Cmd + Option + J (Mac).
Errors would be listed in red in the console.
Thanks for the reply. Yes, the Chrome console is showing the following:
[1st chunk of URL]/WebHelp/whxdata/topictable_12_xml.js
Failed to load resource: the server responded with a status of 404 (Not Found)
Uncaught TypeError: Cannot read property 'toUpperCase' of undefined whutils.js:149
Seems like WebHelp output was not copied to the web server completely.
File topictable_12_xml.js contains part of the search database.
Since the output works fine locally, this indicates some issue with server upload.
You could just try to upload "topictable_12_xml.js" to the server at location "[1st chunk of URL]/WebHelp/whxdata/topictable_12_xml.js" and see if it succeeds.
Did you get a chance to test out the fix I mentioned last week?
You're right that some of the files were missing from the server copy of the WebHelp output. I've copied the missing files over to the server, and am currently working with the team to get this new WebHelp deployed so I can check it. I'm cautiously optimistic that this will fix the problem, and hope to know for certain soon...
Hi Mr .Flibble,
Please let us know of your findings, so we can update the log at our end.
We finally got the corrected version deployed, and it's working great. Thanks again for the help, Ankit!
Glad to know it works. Thanks for the update.