Search Results Page (screen layout component)
The default Search Results Page screen layout provides the following components for each topic when a user performs a search:
(Topic title formatted as a clickable link)
(Topic file path and file name)
(First 100 words in topic: <?rh-msp-search-result-context class="wSearchContext" ?>)
By default, the First 100 words in topic component starts with the topic title. This is redundant. It already appears as a clickable link and (to some degree) in the file path/name. I would like to exclude the title from the First 100 words in topic component. The topics in our project auto-display the title using the RoboHelp title field/variable, so I'm hoping there's a way to specify programmatically/code-wise something like: "For wSearchContext exclude rh_variable_title". I'm not a developer, so I don't know if this is possible and if so how. But if there's a way to do it and someone can tell me how to do it, I am comfortable editing project files (even stuff like search.js or constants.js) to do it.
I appreciate any feedback!
This is a bug that was solved in RoboHelp 2015. In the meanwhile, you can change the contact after generation, but you'll probably would want to automate it somehow. If you open one of the 'topictable_x_xml.js files, you'll find the preview information as shown in the search results. The ct attribute is the sample text and it statert with the topic title. You can change the text there. Far from ideal and you will have to repeat the fix whenever you generate. But that's the only way to fix it that I am aware of.
That did it! I agree, far from ideal, but at least there's a way. Not sure I'll do it - probably better to try to convince management to upgrade to RH 2015.
Good stuff, nonetheless!
If this was fixed in Robohelp 2015, how come I am having the same issue in Robohelp 2017? Is there a way to get around this because repeating the title in the context is taking up space and making the context not very useful. I am willing to make changes in the code/files to sort this but can't seem to find where to sort this out.
If your RH2017 is patched up to date and it's still happening, log a bug with the Adobe Tracker with a link to this thread. I may have been busted after it was fixed in RH2015.