Community
Participate
Working Groups
The help in Helios on uninstalling a feature/plugin is out of date (incorrect). 1. Go to Help > Search 2. For the search expression, type "uninstall feature" 3. Click on the first hit (Enabling, disabling, and uninstalling features). Note the content is incorrect 4. Click on another hit: "Uninstalling software" Note the content is incorrect
Chris, would you know a trick that would cause the p2 doc to come back first over the update manager one when I do the search mentioned in comment #0. For example can I use some meta tag, or something like that? Thx
The keyword meta tag would help boost your search ranking, for example <meta name="keywords" content="uninstall,install"> I don't know if that will be enough to boost your page to the top, if not the <title> element has the highest weight so you can either try to boost your page or lower the rank of the classic update manager page by modifying the <title> element.
I've improved the ranking by adding the tags suggested by Chris. When searching for "uninstall feature", the p2 page comes up second. When I search for uninstall, it comes up first. Chris, is there a way to tell the indexer to skip certain files by adding some markup in them? After all since we don't want to promote update, we could still leave the doc referenced from the TOC but not have it indexed. Chris, what do you think?
There is not a good way to tell the indexer to exclude specific files. About the only thing that you can do is to change the <title> elements in the classic update manager pages to be less informative, for example instead of <title>Using the classic update manager</title> use <title>Classic update manager</title>
Copying Chris Austin for comment. This seems like it is related to Bug 320669 in that if we could add a filter to lower the scores by 25% for search hits within disabled capabilities ( classic update manager is not enabled by default in the SDK ) the P2 hit would be back on top of the list of results. Alternatively the logic to lower the score for the hits could be added to SearchHits.addHits().
No plan to fix this.
