Changes between Version 2 and Version 3 of TracLinks


Ignore:
Timestamp:
Oct 18, 2009 4:54:12 PM (10 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracLinks

    v2 v3  
    11= Trac Links =
     2[[TracGuideToc]]
     3
    24TracLinks 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.
    35
     
    68also have short-hand notations.
    79
     10== Where to use TracLinks ==
     11You can use TracLinks in:
     12
     13 * Source code (Subversion) commit messages
     14 * Wiki pages
     15 * Full descriptions for tickets, reports and milestones
     16
     17and any other text fields explicitly marked as supporting WikiFormatting.
     18
    819Some examples:
    920 * Tickets: '''!#1''' or '''!ticket:1'''
    10  * Ticket comments: '''!comment:ticket:1:2'''
     21 * Ticket comments: '''!comment:1:ticket:2'''
    1122 * Reports: '''!{1}''' or '''!report:1'''
    1223 * Changesets: '''!r1''', '''![1]''', '''!changeset:1''' or (restricted) '''![1/trunk]''', '''!changeset:1/trunk'''
    13  * Revision log: '''!r1:3''', '''![1:3]''' or '''!log:@1:3''', '''!log:trunk@1:3'''
    14  * Diffs (requires [milestone:0.10 0.10]): '''!diff:@1:3''', '''!diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default''' or '''!diff:trunk/trac@3538//sandbox/vc-refactoring@3539'''
     24 * Revision log: '''!r1:3''', '''![1:3]''' or '''!log:@1:3''', '''!log:trunk@1:3''', '''![2:5/trunk]'''
     25 * Diffs (requires [trac:milestone:0.10 0.10]): '''!diff:@1:3''', '''!diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default''' or '''!diff:trunk/trac@3538//sandbox/vc-refactoring@3539'''
    1526 * Wiki pages: '''!CamelCase''' or '''!wiki:CamelCase'''
     27 * Parent page: '''![..]'''
    1628 * Milestones: '''!milestone:1.0'''
    17  * Attachment: '''!attachment:ticket:944:attachment.1073.diff'''
     29 * Attachment: '''!attachment:example.tgz''' (for current page attachment), '''!attachment:attachment.1073.diff:ticket:944'''
     30(absolute path)
    1831 * Files: '''!source:trunk/COPYING'''
    1932 * A specific file revision: '''!source:/trunk/COPYING@200'''
     
    2134Display:
    2235 * Tickets: #1 or ticket:1
    23  * Ticket comments: comment:ticket:1:2
     36 * Ticket comments: comment:1:ticket:2
    2437 * Reports: {1} or report:1
    25  * Changesets: r1, [1], changeset:1, or (restricted) [1/trunk], changeset:1/trunk
    26  * Revision log: r1:3, [1:3] or log:@1:3, log:trunk@1:3
    27  * Diffs (requires [milestone:0.10 0.10]): diff:@20:30, diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default or diff:trunk/trac@3538//sandbox/vc-refactoring/trac@3539
     38 * Changesets: r1, [1], changeset:1 or (restricted) [1/trunk], changeset:1/trunk
     39 * Revision log: r1:3, [1:3] or log:@1:3, log:trunk@1:3, [2:5/trunk]
     40 * Diffs (requires [milestone:0.10 0.10]): diff:@1:3, diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default or diff:trunk/trac@3538//sandbox/vc-refactoring@3539
    2841 * Wiki pages: CamelCase or wiki:CamelCase
     42 * Parent page: [..]
    2943 * Milestones: milestone:1.0
    30  * Attachment: attachment:ticket:944:attachment.1073.diff
     44 * Attachment: attachment:example.tgz (for current page attachment), attachment:attachment.1073.diff:ticket:944
     45(absolute path)
    3146 * Files: source:trunk/COPYING
    3247 * A specific file revision: source:/trunk/COPYING@200
     
    4762Display: [ticket:1 This is a link to ticket number one].
    4863
    49 If the title is be omitted, only the id (the part after the colon) is displayed:
     64If the title is omitted, only the id (the part after the colon) is displayed:
    5065
    5166{{{
     
    6580TracLinks 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.
    6681
    67 The following sections describe the individual link types in detail, as well as several notes advanced usage of links.
    68 
    69 == attachment: links ==
    70 
    71 The link syntax for attachments is as follows:
    72  * !attachment:the_file.txt creates a link to the attachment the_file.txt of the current object
    73  * !attachment:wiki:MyPage:the_file.txt creates a link to the attachment the_file.txt of the !MyPage wiki page
    74  * !attachment:ticket:753:the_file.txt creates a link to the attachment the_file.txt of the ticket 753
    75 
    76 == source: links ==
    77 
    78 The default behavior for a source:/some/path link is to open the directory browser
    79 if the path points to a directory and otherwise open the log view.
    80 It's also possible to link directly to a specific revision of a file like this: source:/some/file@123
    81 or like this to link to the latest revision: source:/some/file@latest.
    82 If the revision is specified, one can even link to a specific line number: source:/some/file@123#L10
    83 
    84 == search: and query: links ==
    85 
    86 See TracSearch#SearchLinks and TracQuery#UsingTracLinks
    87 
    88 == !SubWiki links ==
    89 To create a SubWiki link to a SubWiki-page just use a '/':
    90 {{{
    91  [wiki:WikiPage/SubWikiPage].
    92 }}}
    93 
    94 == InterWiki links ==
     82
     83== Advanced use of TracLinks ==
     84
     85=== Relative links ===
     86
     87To create a link to a specific anchor in a page, use '#':
     88{{{
     89 [#Relativelinks relative links]
     90}}}
     91Displays:
     92  [#Relativelinks relative links]
     93
     94Hint: 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.
     95
     96To create a link to a [trac:SubWiki SubWiki]-page just use a '/':
     97{{{
     98 WikiPage/SubWikiPage or ./SubWikiPage
     99}}}
     100
     101To link from a [trac:SubWiki SubWiki] page to a parent, simply use a '..':
     102{{{
     103  [..]
     104}}}
     105
     106To link from a [trac:SubWiki SubWiki] page to a sibling page, use a '../':
     107{{{
     108  [../Sibling see next sibling]
     109}}}
     110
     111''(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 now in 0.11 it will stay in the wiki namespace and link to a sibling page. See [#Server-relativelinks] for the new syntax.
     112
     113=== InterWiki links ===
    95114
    96115Other 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.
    97116
    98 == InterTrac links ==
    99 
    100 Any of the above form of Trac links could be written in one Trac environment and actually refer to resources present in another Trac environment, provided the Trac link is prefixed by the name of that other Trac environment followed by a colon. That other Trac environment must be registered. See InterTrac for details.
    101 
    102 
    103 == Server-relative links ==
    104 
    105 It is often useful to be able to link to objects on your server that have no built-in
    106 Trac linking mechanism, such as static resources, a `/register` page, etc. This
    107 can be achieved by simply using either an absolute path from the server root,
    108 or a relative link from the URL of the current page:
    109 
    110 {{{
    111 [../newticket newticket]
     117=== InterTrac links ===
     118
     119This can be seen as a kind of InterWiki link specialized for targeting other Trac projects.
     120
     121Any type of Trac links could be written in one Trac environment and actually refer to resources present in another Trac environment, provided the Trac link is prefixed by the name of that other Trac environment followed by a colon. That other Trac environment must be registered, under its name or an alias. See InterTrac for details.
     122
     123A distinctive advantage of InterTrac links over InterWiki links is that the shorthand form of Trac links usually have a way to understand the InterTrac prefixes. For example, links to Trac tickets can be written #T234 (if T was set as an alias for Trac), links to Trac changesets can be written [trac 1508].
     124
     125=== Server-relative links ===
     126
     127It is often useful to be able to link to objects in your project that
     128have no built-in Trac linking mechanism, such as static resources, `newticket`,
     129a shared `/register` page on the server, etc.
     130
     131To link to resources inside the project, use either an absolute path from the project root,
     132or a relative link from the URL of the current page (''Changed in 0.11''):
     133
     134{{{
     135[/newticket Create a new ticket]
    112136[/ home]
    113137}}}
    114138
    115 Display: [../newticket newticket] [/ home]
    116 
    117 == Quoting space in TracLinks ==
     139Display: [/newticket newticket] [/ home]
     140
     141To link to another location on the server (outside the project), use the '//location' link syntax (''Changed in 0.11''):
     142
     143{{{
     144[//register Register Here]
     145}}}
     146
     147Display: [//register Register Here]
     148
     149=== Quoting space in TracLinks ===
    118150
    119151Immediately after a TracLinks prefix, targets containing space characters should
     
    123155 * !attachment:'the file.txt' or
    124156 * !attachment:"the file.txt"
    125  * !attachment:"ticket:123:the file.txt"
    126 
    127 == Where to use TracLinks ==
    128 You can use TracLinks in:
    129 
    130  * Source code (Subversion) commit messages
    131  * Wiki pages
    132  * Full descriptions for tickets, reports and milestones
    133 
    134 and any other text fields explicitly marked as supporting WikiFormatting.
    135 
    136 == Escaping Links ==
     157 * !attachment:"the file.txt:ticket:123"
     158
     159=== Escaping Links ===
    137160
    138161To prevent parsing of a !TracLink, you can escape it by preceding it with a '!' (exclamation mark).
     
    146169 ![42] is not a link either.
    147170
     171
     172=== Parameterized Trac links ===
     173
     174The Trac links target Trac resources which have generally more than one way to be rendered, according to 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.
     175
     176Any Trac links can support an arbitrary set of parameters, written in the same way as they would be for the corresponding URL. Some examples:
     177 - `wiki:WikiStart?format=txt`
     178 - `ticket:1?version=1`
     179 - `[/newticket?component=module1 create a ticket for module1]`
     180
     181
     182== TracLinks Reference ==
     183The following sections describe the individual link types in detail, as well as several notes advanced usage of links.
     184
     185=== attachment: links ===
     186
     187The link syntax for attachments is as follows:
     188 * !attachment:the_file.txt creates a link to the attachment the_file.txt of the current object
     189 * !attachment:the_file.txt:wiki:MyPage creates a link to the attachment the_file.txt of the !MyPage wiki page
     190 * !attachment:the_file.txt:ticket:753 creates a link to the attachment the_file.txt of the ticket 753
     191
     192Note that the older way, putting the filename at the end, is still supported: !attachment:ticket:753:the_file.txt.
     193
     194If 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:`.
     195
     196This 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.
     197
     198See also [#export:links].
     199
     200=== comment: links ===
     201
     202When you're inside a given tickets, you can simply write e.g. !comment:3 to link to the third change comment.
     203It's also possible to link to a comment of a specific ticket from anywhere using one of the following syntax:
     204 - !comment:3:ticket:123
     205 - !ticket:123#comment:3 (note that you can't write !#123#!comment:3!)
     206
     207=== query: links ===
     208
     209See TracQuery#UsingTracLinks and [#ticket:links].
     210
     211=== search: links ===
     212
     213See TracSearch#SearchLinks
     214
     215=== ticket: links ===
     216
     217Besides 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.
     218
     219Example:
     220 - `ticket:5000-6000`
     221 - `ticket:1,150`
     222
     223''(since Trac 0.11)''
     224
     225=== timeline: links ===
     226
     227Links 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.
     228
     229Examples:
     230 - `timeline:2008-01-29`
     231 - `timeline:2008-01-29T15:48`
     232 - `timeline:2008-01-29T16:48Z+01`
     233
     234''(since Trac 0.11)''
     235
     236=== wiki: links ===
     237
     238See WikiPageNames and [#QuotingspaceinTracLinks quoting space in TracLinks] above.
     239
     240=== Version Control related links ===
     241==== source: links ====
     242
     243The default behavior for a source:/some/path link is to open the directory browser
     244if the path points to a directory and otherwise open the log view.
     245
     246It's also possible to link directly to a specific revision of a file like this:
     247 - `source:/some/file@123` - link to the file's revision 123
     248 - `source:/some/file@head` - link explicitly to the latest revision of the file
     249
     250If the revision is specified, one can even link to a specific line number:
     251 - `source:/some/file@123#L10`
     252 - `source:/tag/0.10@head#L10`
     253
     254Finally, one can also highlight an arbitrary set of lines:
     255 - `source:/some/file@123:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103.
     256''(since 0.11)''
     257
     258==== export: links ====
     259
     260To 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:
     261 * `export:/some/file` - get the HEAD revision of the specified file
     262 * `export:123:/some/file` - get revision 123 of the specified file
     263 * `export:/some/file@123` - get revision 123 of the specified file
     264
     265This 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.
     266
     267If 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`).
     268
     269==== log: links ====
     270
     271The `log:` links are used to display revision ranges. In its simplest form, it can link to the latest revisions from the specified path, but it can also support displaying an arbitrary set of revisions.
     272 - `log:/` - the latest revisions starting at the root of the repository
     273 - `log:/trunk/tools` - the latest revisions in `trunk/tools`
     274 - `log:/trunk/tools@10000` - the revisions in `trunk/tools` starting from  revision 10000
     275 - `log:@20788,20791:20795` - list revision 20788 and the 20791 to 20795 revision range
     276 - `log:/trunk/tools@20788,20791:20795` - list revision 20788 and the revisions from the 20791 to 20795 range which affect the given path
     277
     278There are short forms for revision ranges as well:
     279 - `[20788,20791:20795]`
     280 - `[20788,20791:20795/trunk/tools]`
     281 - `r20791:20795` (but not `r20788,20791:20795` nor `r20791:20795/trunk`)
     282
     283Finally, note that in all of the above, a revision range can be written indifferently `x:y` or `x-y`.
     284
    148285----
    149286See also: WikiFormatting, TracWiki, WikiPageNames, InterTrac, InterWiki