Edgewall Software

Changes between Initial Version and Version 10 of 0.12/TracLinks

(multiple changes)
(multiple changes)
(multiple changes)


  • 0.12/TracLinks

    v1 v10  
     1= Trac Links =
     5TracLinks are a fundamental feature of Trac, because they allow easy hyperlinking between the various entities in the system—such as tickets, reports, changesets, Wiki pages, milestones, and source files—from anywhere WikiFormatting is used.
     7TracLinks are generally of the form '''type:id''' (where ''id'' represents the
     8number, name or path of the item) though some frequently used kinds of items
     9also have short-hand notations.
     11== Where to use TracLinks ==
     12You can use TracLinks in:
     14 * Source code (Subversion) commit messages
     15 * Wiki pages
     16 * Full descriptions for tickets, reports and milestones
     18and any other text fields explicitly marked as supporting WikiFormatting.
     20== Overview ==
     22||= Wiki Markup =||= Display =||
     24 Wiki pages :: `CamelCase` or `wiki:CamelCase`
     25 Parent page :: `[..]`
     26 Tickets :: `#1` or `ticket:1`
     27 Ticket comments :: `comment:1:ticket:2`
     28 Reports :: `{1}` or `report:1`
     29 Milestones :: `milestone:1.0`
     30 Attachment :: `attachment:example.tgz` (for current page attachment), `attachment:attachment.1073.diff:ticket:944` (absolute path)
     31 Changesets :: `r1`, `[1]`, `changeset:1` or (restricted) `[1/trunk]`, `changeset:1/trunk`
     32 Revision log :: `r1:3`, `[1:3]` or `log:@1:3`, `log:trunk@1:3`, `[2:5/trunk]`
     33 Diffs :: `diff:@1:3`, `diff:plugins/0.12/mercurial-plugin@9128:9953`,
     34          `diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default`
     35          or `diff:trunk/trac@3538//sandbox/vc-refactoring@3539`
     36 Files :: `source:trunk/COPYING`, `source:/trunk/COPYING@200` (at version 200), `source:/trunk/COPYING@200#L25` (at version 200, line 25)
     39 Wiki pages :: CamelCase or wiki:CamelCase
     40 Parent page :: [..]
     41 Tickets :: #1 or ticket:1
     42 Ticket comments :: comment:1:ticket:2
     43 Reports :: {1} or report:1
     44 Milestones :: milestone:1.0
     45 Attachment :: attachment:example.tgz (for current page attachment), attachment:attachment.1073.diff:ticket:944 (absolute path)
     46 Changesets :: r1, [1], changeset:1 or (restricted) [1/trunk], changeset:1/trunk
     47 Revision log :: r1:3, [1:3] or log:@1:3, log:trunk@1:3, [2:5/trunk]
     48 Diffs :: diff:@1:3, diff:plugins/0.12/mercurial-plugin@9128:9953,
     49          diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default
     50          or diff:trunk/trac@3538//sandbox/vc-refactoring@3539
     51 Files :: source:trunk/COPYING, source:/trunk/COPYING@200 (at version 200), source:/trunk/COPYING@200#L25 (at version 200, line 25)
     54'''Note:''' The wiki:CamelCase form is rarely used, but it can be convenient to refer to
     55pages whose names do not follow WikiPageNames rules, i.e., single words,
     56non-alphabetic characters, etc. See WikiPageNames for more about features specific
     57to links to Wiki page names.
     60{{{#!table class=""
     61|||| Trac links using the full (non-shorthand) notation can also be given a custom link title like this: ||
     64[ticket:1 This is a link to ticket number one] or
     65[[ticket:1|This is another link to ticket number one]].
     69[ticket:1 This is a link to ticket number one] or
     70[[ticket:1|This is another link to ticket number one]].
     73|||| If the title is omitted, only the id (the part after the colon) is displayed:  ||
     76[ticket:1] or [[ticket:2]]
     80[ticket:1] or [[ticket:2]]
     83|||| `wiki` is the default if the namespace part of a full link is omitted:  ||
     86[SandBox the sandbox] or
     87[[SandBox|the sandbox]]
     91[SandBox the sandbox] or
     92[[SandBox|the sandbox]]
     95|||| The short form ''realm:target'' can also be wrapped within a <...> pair, [[br]] which allow for arbitrary characters (i.e. anything but >)  ||
     106TracLinks are a very simple idea, but actually allow quite a complex network of information. In practice, it's very intuitive and simple to use, and we've found the "link trail" extremely helpful to better understand what's happening in a project or why a particular change was made.
     109== Advanced use of TracLinks ==
     111=== Relative links ===
     113To create a link to a specific anchor in a page, use '#':
     115 [#Relativelinks relative links] or [[#Relativelinks|relative links]]
     118  [#Relativelinks relative links] or [[#Relativelinks|relative links]]
     120Hint: when you move your mouse over the title of a section, a '¶' character will be displayed. This is a link to that specific section and you can use this to copy the `#...` part inside a relative link to an anchor.
     122To create a link to a [trac:SubWiki SubWiki]-page just use a '/':
     124 WikiPage/SubWikiPage or ./SubWikiPage
     127To link from a [trac:SubWiki SubWiki] page to a parent, simply use a '..':
     129  [..] or [[..]]
     131  [..] or [[..]]
     133To link from a [trac:SubWiki SubWiki] page to a [=#sibling sibling] page, use a '../':
     135  [../Sibling see next sibling] or [[../Sibling|see next sibling]]
     137  [../Sibling see next sibling] or [[../Sibling|see next sibling]]
     139But in practice you often won't need to add the `../` prefix to link to a sibling page.
     140For resolving the location of a wiki link, it's the target page closest in the hierarchy
     141to the page where the link is written which will be selected. So for example, within
     142a sub-hierarchy, a sibling page will be targeted in preference to a toplevel page.
     143This makes it easy to copy or move pages to a sub-hierarchy by [[WikiNewPage#renaming|renaming]] without having to adapt the links.
     145In order to link explicitly to a [=#toplevel toplevel] Wiki page,
     146use the `wiki:/` prefix.
     147Be careful **not** to use the `/` prefix alone, as this corresponds to the
     148[#Server-relativelinks] syntax and with such a link you will lack the `/wiki/`
     149part in the resulting URL.
     151''(Changed in 0.11)'' Note that in Trac 0.10, using e.g. `[../newticket]`  may have worked for linking to the `/newticket` top-level URL, but since 0.11, such a link will stay in the wiki namespace and therefore link to a sibling page.
     152See [#Server-relativelinks] for the new syntax.
     154=== InterWiki links ===
     156Other prefixes can be defined freely and made to point to resources in other Web applications. The definition of those prefixes as well as the URLs of the corresponding Web applications is defined in a special Wiki page, the InterMapTxt page. Note that while this could be used to create links to other Trac environments, there's a more specialized way to register other Trac environments which offers greater flexibility.
     158=== InterTrac links ===
     160This can be seen as a kind of InterWiki link specialized for targeting other Trac projects.
     162Any type of Trac link can be written in one Trac environment and actually refer to resources in another Trac environment. All that is required is to prefix the Trac link with the name of the other Trac environment followed by a colon. The other Trac environment must be registered on the InterTrac page.
     164A distinctive advantage of InterTrac links over InterWiki links is that the shorthand form of Trac links (e.g. `{}`, `r`, `#`) can also be used. For example if T was set as an alias for Trac, links to Trac tickets can be written #T234, links to Trac changesets can be written [trac 1508].
     165See InterTrac for the complete details.
     167=== Server-relative links ===
     169It is often useful to be able to link to objects in your project that
     170have no built-in Trac linking mechanism, such as static resources, `newticket`,
     171a shared `/register` page on the server, etc.
     173To link to resources inside the project, use either an absolute path from the project root,
     174or a relative link from the URL of the current page (''Changed in 0.11''):
     177[/newticket Create a new ticket] or [[//newticket|Create a new ticket]]
     178[/ home] or [[/|home]]
     181Display: [/newticket Create a new ticket] or [[//newticket|Create a new ticket]]
     182[/ home] or [[/|home]]
     184To link to another location on the server (possibly outside the project but on the same host), use the `//` prefix (''Changed in 0.11''):
     187[//register Register Here] or [[//register|Register Here]]
     190Display: [//register Register Here] or [[//register|Register Here]]
     192=== Quoting space in TracLinks ===
     194Immediately after a TracLinks prefix, targets containing space characters should
     195be enclosed in a pair of quotes or double quotes.
     197 * !wiki:"The whitespace convention"
     198 * !attachment:'the file.txt' or
     199 * !attachment:"the file.txt"
     200 * !attachment:"the file.txt:ticket:123"
     202Note that by using [trac:WikiCreole] style links, it's quite natural to write links containing spaces:
     203 * ![[The whitespace convention]]
     204 * ![[attachment:the file.txt]]
     206=== Escaping Links ===
     208To prevent parsing of a !TracLink, you can escape it by preceding it with a '!' (exclamation mark).
     210 !NoLinkHere.
     211 ![42] is not a link either.
     215 !NoLinkHere.
     216 ![42] is not a link either.
     219=== Parameterized Trac links ===
     221Many Trac resources have more than one way to be rendered, depending on some extra parameters. For example, a Wiki page can accept a `version` or a `format` parameter, a report can make use of dynamic variables, etc.
     223Trac links can support an arbitrary set of parameters, written in the same way as they would be for the corresponding URL. Some examples:
     224 - `wiki:WikiStart?format=txt`
     225 - `ticket:1?version=1`
     226 - `[/newticket?component=module1 create a ticket for module1]`
     227 - `[/newticket?summary=Add+short+description+here create a ticket with URL with spaces]`
     230== TracLinks Reference ==
     231The following sections describe the individual link types in detail, as well as notes on advanced usage of links.
     233=== attachment: links ===
     235The link syntax for attachments is as follows:
     236 * !attachment:the_file.txt creates a link to the attachment the_file.txt of the current object
     237 * !attachment:the_file.txt:wiki:MyPage creates a link to the attachment the_file.txt of the !MyPage wiki page
     238 * !attachment:the_file.txt:ticket:753 creates a link to the attachment the_file.txt of the ticket 753
     240Note that the older way, putting the filename at the end, is still supported: !attachment:ticket:753:the_file.txt.
     242If you'd like to create a direct link to the content of the attached file instead of a link to the attachment page, simply use `raw-attachment:` instead of `attachment:`.
     244This can be useful for pointing directly to an HTML document, for example. Note that for this use case, you'd have to allow the web browser to render the content by setting `[attachment] render_unsafe_content = yes` (see TracIni#attachment-section). Caveat: only do that in environments for which you're 100% confident you can trust the people who are able to attach files, as otherwise this would open up your site to [wikipedia:Cross-site_scripting cross-site scripting] attacks.
     246See also [#export:links].
     248=== comment: links ===
     250When you're inside a given ticket, you can simply write e.g. !comment:3 to link to the third change comment.
     251It is possible to link to a comment of a specific ticket from anywhere using one of the following syntax:
     252 - `comment:3:ticket:123`
     253 - `ticket:123#comment:3` (note that you can't write `#123#!comment:3`!)
     254It is also possible to link to the ticket's description using one of the following syntax:
     255 - `comment:description` (within the ticket)
     256 - `comment:description:ticket:123`
     257 - `ticket:123#comment:description`
     259=== htdocs: links ===
     261Use `htdocs:path/to/file` to reference files in the `htdocs` directory of the Trac environment, the [TracEnvironment#DirectoryStructure web resource directory].
     263=== query: links ===
     265See TracQuery#UsingTracLinks and [#ticket:links].
     267=== search: links ===
     269See TracSearch#SearchLinks
     271=== ticket: links ===
     272 ''alias:'' `bug:`
     274Besides the obvious `ticket:id` form, it is also possible to specify a list of tickets or even a range of tickets instead of the `id`. This generates a link to a custom query view containing this fixed set of tickets.
     277 - `ticket:5000-6000`
     278 - `ticket:1,150`
     280''(since Trac 0.11)''
     282=== timeline: links ===
     284Links to the timeline can be created by specifying a date in the ISO:8601 format. The date can be optionally followed by a time specification. The time is interpreted as being UTC time, but alternatively you can specify your local time, followed by your timezone if you don't want to compute the UTC time.
     287 - `timeline:2008-01-29`
     288 - `timeline:2008-01-29T15:48`
     289 - `timeline:2008-01-29T15:48Z`
     290 - `timeline:2008-01-29T16:48+01`
     292''(since Trac 0.11)''
     294=== wiki: links ===
     296See WikiPageNames and [#QuotingspaceinTracLinks quoting space in TracLinks] above. It is possible to create a link to a specific page revision using the syntax WikiStart@1.
     298=== Version Control related links ===
     300It should be noted that multiple repository support works by creating a kind of virtual namespace for versioned files in which the toplevel folders correspond to the repository names. Therefore, in presence of multiple repositories, a ''/path'' specification in the syntax of links detailed below should start with the name of the repository. If omitted, the default repository is used. In case a toplevel folder of the default repository has the same name as a repository, the latter "wins". One can always access such folder by fully qualifying it (the default repository can be an alias of a named repository, or conversely, it is always possible to create an alias for the default repository, ask your Trac administrator).
     302For example, `source:/trunk/COPYING` targets the path `/trunk/COPYING` in the default repository, whereas `source:/projectA/trunk/COPYING` targets the path `/trunk/COPYING` in the repository named `projectA`. This can be the same file if `'projectA'` is an alias to the default repository or if `''` (the default repository) is an alias to `'projectA'`.
     304==== source: links ====
     305 ''aliases:'' `browser:`, `repos:`
     307The default behavior for a source:/some/path link is to open the browser in that directory directory
     308if the path points to a directory or to show the latest content of the file.
     310It's also possible to link directly to a specific revision of a file like this:
     311 - `source:/some/file@123` - link to the file's revision 123
     312 - `source:/some/file@head` - link explicitly to the latest revision of the file
     314If the revision is specified, one can even link to a specific line number:
     315 - `source:/some/file@123#L10`
     316 - `source:/tag/0.10@head#L10`
     318Finally, one can also highlight an arbitrary set of lines:
     319 - `source:/some/file@123:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103.
     320   ''(since 0.11)''
     322Note that in presence of multiple repositories, the name of the repository is simply integrated in the path you specify for `source:` (e.g. `source:reponame/trunk/README`). ''(since 0.12)''
     324==== export: links ====
     326To force the download of a file in the repository, as opposed to displaying it in the browser, use the `export` link.  Several forms are available:
     327 * `export:/some/file` - get the HEAD revision of the specified file
     328 * `export:123:/some/file` - get revision 123 of the specified file
     329 * `export:/some/file@123` - get revision 123 of the specified file
     331This can be very useful for displaying XML or HTML documentation with correct stylesheets and images, in case that has been checked in into the repository. Note that for this use case, you'd have to allow the web browser to render the content by setting `[browser] render_unsafe_content = yes` (see TracIni#browser-section), otherwise Trac will force the files to be downloaded as attachments for security concerns.
     333If the path is to a directory in the repository instead of a specific file, the source browser will be used to display the directory (identical to the result of `source:/some/dir`).
     335==== log: links ====
     337The `log:` links are used to display revision ranges. In its simplest form, it can link to the latest revisions of the specified path, but it can also support displaying an arbitrary set of revisions.
     338 - `log:/` - the latest revisions starting at the root of the repository
     339 - `log:/trunk/tools` - the latest revisions in `trunk/tools`
     340 - `log:/trunk/tools@10000` - the revisions in `trunk/tools` starting from  revision 10000
     341 - `log:@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795
     342 - `log:/trunk/tools@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795 which affect the given path
     344There are short forms for revision ranges as well:
     345 - `[20788,20791:20795]`
     346 - `[20788,20791:20795/trunk/tools]`
     347 - `r20791:20795` (but not `r20788,20791:20795` nor `r20791:20795/trunk`)
     349Finally, note that in all of the above, a revision range can be written either as `x:y` or `x-y`.
     351In the presence of multiple repositories, the name of the repository should be specified as the first part of the path, e.g. `log:repos/branches` or `[20-40/repos]`.
     354See also: WikiFormatting, TracWiki, WikiPageNames, InterTrac, InterWiki