Online help search not working....

[nba_fortra]

After upgrading RH to 2022.0.346 from 2017, search is not working in our online help in our browser-based management app. Search works in the output English Web Help locally (on my PC) but not when the output files are part of our context-sensitive online help system in our management console. This worked properly with the output from RH 2017. We get this error in the dev console when we enter a search term in the Search box:

"return a.onkeyup=function(a){if(!f||f===a.keyCode)return e.call(c,a,a.currentTarget)}}},{key:"data_scroll",value:function(a,b){var c=this,d=this._data_event_callback(b),e=d.opts,f=e&&e.delta||..."

in rh.min.js

We open the help in a new browser window. If we refresh the window, the search results show up. I added a screenshot of the error.  I tried removing the .gz files as noted elsewhere--made the problem worse. Now refreshing the window does not show the returned results. 

Help.

[Jeff_Coatsworth]

If it's working locally & not on the webserver, then I would suspect that something isn't in synch with the server. have you tried deleting all the files off the web server & re-uploading them? Did you create a new Preset in 2022 after upgrading the RH2017 project?

[nba_fortra]

 I did create a new preset. I did  not rip and replace all the files. Have to give that a try in our test environment. We'll see what happens if I do that. Thanks.

[nba_fortra]

I tried removing and replacing all the help files. No difference--search still does not work. I'll try deleting and recreating my preset too. Any other suggestions for next experiments? Thanks.

[Jeff_Coatsworth]

Hmm, bizarre - what about testing with the sample project? You've enabled JavaScript on the web server right?

[nba_fortra]

Yes. The new preset did not help. Not sure how I could test with the sample project.... Guidance?

[Jeff_Coatsworth]

There should be a sample project in your Documents\My RoboHelp Projects folder

[nba_fortra]

Solution seems to be to do the project upgrade from 2017 to 2022 by sequentially upgrading the project to 2019, then 2020, then on to 2022. Now works with a few little glitches. Like the CSS file doesn't seem to be used so the look and feel is off. But that minor compared to the content and search.