This issue arises from this issue, summarized here.
In brief: for the Token Filter module, the short-form tips for the text filter, which appears in the "Formatting options" fieldset, doesn't show what tokens can be used. The long-form tips, which appears on the "Compose tips" page for the format (at path /filter/tips/<format>
), includes the relevant token browser. This situation led to the realization that in general, there's no easy way to go to the "Compose tips" page for a text format or otherwise see the long-form tips from the "Formatting options" fieldset, or for a user to even know that more tips information is available.
A simple fix might be to simply add to the bottom of the short-form tips a link to the long-form "Compose tips" page, called something like "more information".
A perhaps nicer fix might be to allow the user to toggle between the short-form and long-form display within "Formatting options", or to toggle the long-form display of tips as an overlay—in either case, avoiding having to leave the page to see the detailed description.
Is this notion worth pursuing? If so, I would be willing to work on a PR.
Recent comments
Try adding to your Views page /hirek Contextual filter "Global: Null". And use a Canonical URL for all pages, which will help eliminate duplicate content for search engines.
Double Triple Category Name
thanks for the advice, I rewrote it, but I can still enter the news category in the search engine 3x 4x news/news/news/ I type as many times as I want
Double Triple Category Name
It turned out that this is not a “term”, but a “page”. Ok. If this is a content type like “News”, it is logical to use the pattern "news/[node:title]" where "news" is a list of all...
Double Triple Category Name