Now we have found that our users’ searches return corrupted results when we have the RH9 server configured for server-side indexing; for example, terms that are clearly present in topics return no results on Search. When we disabled server-side indexing, and republished, the search results performed correctly.

As I reported here earlier, we continue to get a corrupted TOC when publishing WebHelp Pro to RH9 Server. Some books and topic nested at level 3 do not appear; sometimes there are visible gaps in the TOC and other times no gaps, just missing content. These errors do not appear in WebHelp output (as distinct from WebHelp Pro) nor do they appear in WebHelp Pro output on my local C: drive. They occur only when WebHelp Pro output is published to the RH9 Server. Last week I sent you a couple of screenshots showing the discrepancy.

I am beginning to wonder whether the WebHelp Pro/Robo Server 9 combination is sufficiently robust.

Much appreciated, John. Will sift through these.

Regarding the nested TOC, it appears to be a combination of number or volume of topics plus the nesting that apparently hits some threshold before it goes haywire. I’ve often built deeply nested structures with no problems (though not using  WebHelpPro for those projects).

Yes, I know about the difference between viewing local output and server output. For example, when viewing local output, the toolbar shows ALL buttons that are available in the skin definition, not just the ones selected in the default window, which are the only ones shown in server output (with the exception of the Search input box in the toolbar which I do NOT want and cannot turn off!).

You mention differences between the two WebHelp types – but from the user’s perspective, what are they really? My understanding is that the analytics are the main differentiator, and of course users aren’t exposed to that. Or are there other behavioural differences visible to users? Because I’m really thinking of backing out of WebHelp Pro for the short term and publishing plain old WebHelp.

Anyway, thanks again for the leads … hoping I hit paydirt soon!

Mike

Just updating this item. The problem afffects WebHelp Pro output regardless of whether that output is published to a server or not. The result in my local !SSL! folder is the same; i.e., some (not all) folders not appearing in the TOC when nested at level 3 and below. I have been advised that the RH engineering team is looking into this and will update this discussion further when I receive any news.

I have also determined that the same problem occurs in WebHelp Pro output when a single TOC is used in the project, or when multiple TOCs are used and merged. The results are the same either way.

The problem does not occur when the same content is generated as WebHelp (not Pro).

Mike

Good to hear, John. I'm wondering if the thread title should be changed to make it clear that it occurs in all WebHelp Pro output irrespective of server publication -- or if it's even possible to do that.

Thanks for letting me know about your interest in this.

I have sent it -- please let me know if anything further is needed, such as screen captures of the results I am seeing. If you carefully examine the difference between the WebHelp TOC and WebHelp Pro TOC then you will see the problem.

Adobe Support has now provided a fix for this bug which appears to resolve it. They will be putting the details on their support pages (not sure where).

Hi John,

Not sure if it is the same. Support sent us a file named SearchUtils.class and it worked. Here are the instructions:

·         Copy this file in the RHS Installed folder at  WEB-INF\classes\adobe\robohelp\server\search folder location

·         Restart the Server

Mike