Search results include: .p.searchsummary0_###

Forum|Forum|4 years ago
October 7, 2021
4 replies
236 views

Good morning all,

My team has published for the first time using RoboHelp 2020! One thing of note is in the projects search results, there is a line of text ".p.searchsummary0_###" where ### is a seemingly random string of numbers. This looks to be related to a wSearchContext span? I have not been able to determine the cause so figured I would post the question here.

Another project with identical settings (as far as I can tell) was published and its search results do not include this string.

Thanks!

This topic has been closed for replies.

Peter Grainge

Community Expert

@defaultyf5en7gttvph

When you say "copy the skin" you do mean just create a fresh copy, correct? Test without any customisation, deal with that later.

"when I enable the Windows web server and dish the help up locally". Do you just mean you upload the local help to the web server or something different, if so what?" Also please confirm it is a web server and not a file server.

As you can see from the date of the original post, this is not a common error.

BTW Your subscription entitles you to install the 2022 version.

________________________________________________________

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

Use menu (bottom right) to mark as Best Answer or to Highlight particularly useful replies. Found the answer elsewhere? Share it here.

D

defaultyf5en7gttvph

Participant

I am running into the same issue with (1) the search result links not actualy working and (2) .p.searchsummary##_## appearing below the dead link.

I am using RoboHelp 2020.8.34 to generate responsive html output as well. Republishing the help did not fix the issue. I made another copy of the output preset, but that had no effect; I will try making a copy of the skin and see if that helps.

Another clue is that the help's search results work correctly when displayed from my local folder, and when I enable the Windows web server and dish the help up locally. So I suspect that there's something happening on the web server where it's broken - maybe a security restriction or something.

TIA for any help!