Is Search broken in RH2020 for Frameless?

[KarenMinOR]

I'm using RH 2020.8.34 Frameless output, and when I use Search, no results are displayed. It shows terms that match my search term, but when I hit Enter, nothing happens. 

Any ideas?

TIA!

[KarenMinOR]

UPDATE

For the fun of it, I enabled Layout > Use skin home page in a "test" frameless output preset, and search works from that. That led me to wonder if I could have messed up the functionality of search with skin edits, so I went back to an older skin, disabled Use skin home page, and regenerated. It seems my skin customizations may have broken Search... 😛 I'll troubleshoot and repost here if I can't fix it, but I'm thinking it's "user configuration error."

[timf33396648]

Hi There! I'm wondering if you had any luck zeroing in on the issue with this. I have an issue with search I'm trying to troubleshoot and this may be involved. Thank you!

[defaultbt4uzj77vtg6]

I haven't found the reason my first set of customizations broke search, but when I started over with customizations, search is still working.

[defaultbt4uzj77vtg6]

Oops. I'm the original poster, KarenMinOR. IDK why it gave me a random handle. 😛

[Peter Grainge]

@timf33396648 What's the issue you are having?

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

[timf33396648]

Thank you @KarenMinOR and @Peter Grainge for your responses.

After some digging around the forum I found this topic about the search database files (Solved: Slow search times for RoboHelp 2020 using Frameles... - Adobe Community - 12719952) which I think relates to my problem.

The symptom *some* of my users experience is that search is non-responsive and crashes the tab. A user will search for something, and the response box displays the number of topics in the search result but never displays the actual results. The tab will time out, and the browser (in our case, Edge) presents a box with options to "Wait" or "Reload", but it's futile as neither option does anything.

After taking on board the conversation in the other thread (linked above), I've been investigating whether the file search_db.js is present for users who experience this issue. So far I've found the reference to that file is missing in the page code for users who cannot search. If this is the case, it seems more likely an issue with our organisation's browser settings than a problem with RoboHelp. But it's inconsistent across my users, so my "search" for a cause and solution is ongoing.

Cheers,

Tim