You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Jon Sime (JIRA)" <ji...@apache.org> on 2016/03/09 22:53:40 UTC
[jira] [Resolved] (TS-4251) doc pages records config search anchors
don't work
[ https://issues.apache.org/jira/browse/TS-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jon Sime resolved TS-4251.
--------------------------
Resolution: Fixed
Took a slightly different approach on this, because the anchors in search results links are generated by the Sphinx search Javascript. I've updated the traffic-server.py domain for config vars to include an additional link ID (it comes through as just a span around the variable's header) which is the unaltered variable name.
> doc pages records config search anchors don't work
> ---------------------------------------------------
>
> Key: TS-4251
> URL: https://issues.apache.org/jira/browse/TS-4251
> Project: Traffic Server
> Issue Type: Bug
> Components: Documentation
> Reporter: Miles Libbey
> Assignee: Jon Sime
> Fix For: Docs
>
>
> When you search for a config, and click on the result, the anchor/hashtag at the end of the url does not match the actual anchor/hashtag on the page. As a result, the page does not focus on the config searched for.
> For example:
> 1) search for proxy.config.bin_path
> (https://docs.trafficserver.apache.org/en/latest/search.html?q=proxy.config.bin_path&check_keywords=yes&area=default)
> 2) Click on the proxy.config.bin_path link
> (https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html?highlight=proxy.config.bin_path#proxy.config.bin_path)
> 3) The records.config page will load, focused on the top of the page.
> If the link used the hashtag #proxy-config-bin-path (instead of #proxy.config.bin_path), it would focus on the right area (https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html?highlight=proxy.config.bin_path#proxy-config-bin-path)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)