Fork me on GitHub

Changes between Version 3 and Version 4 of InterTrac


Ignore:
Timestamp:
Aug 1, 2024, 10:29:22 AM (4 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • InterTrac

    v3 v4  
    11= InterTrac Links
    22
    3 Trac supports a convenient way to refer to resources of other Trac servers, from within the Wiki markup. An !InterTrac link can be seen as a scoped TracLinks. It is used for referring to a Trac resource located in another Trac environment. A resource can be a wiki page, changeset, ticket or milestone.
    4 
    5 == List of Active InterTrac Prefixes
    6 
    7 [[InterTrac]]
     3Trac supports a convenient way to refer to resources of other Trac servers using Wiki markup. An !InterTrac link can be seen as a scoped [TracLinks TracLink]. It is used for referring to a Trac resource located in another Trac environment.
    84
    95== Link Syntax
     
    1511}}}
    1612
    17 The other resource is specified using a regular TracLinks, of any flavor.
     13The other resource is specified using a regular !TracLink, of any flavor.
    1814
    19 That target environment name is either the real name of the environment or an alias for it.
     15That target environment name is either the real name of the environment or an alias.
    2016The aliases are defined in the `trac.ini` file, see below.
    2117The prefix is case insensitive.
    2218
    23 If the InterTrac link is enclosed in square brackets, like `[th:WikiExtrasPlugin]`, the InterTrac prefix is removed in the displayed link like a normal link resolver would be, ie the above would be displayed as `WikiExtrasPlugin`.
     19If the InterTrac link is enclosed in square brackets, like `[th:WikiExtrasPlugin]`, the InterTrac prefix is removed in the displayed link like a normal link resolver would be. For example, the above would be displayed as `WikiExtrasPlugin`.
    2420
    25 For convenience, there is also an alternative short-hand form, where an alias can be used as an immediate prefix for the identifier of a ticket, changeset or report, eg `#T234`, `[T1508]`, `[trac 1508]`.
     21For convenience, there is also an alternate short-hand form, where an alias can be used as an immediate prefix for the identifier of a ticket, changeset or report, eg `#T234`, `[T1508]`, `[trac 1508]`.
    2622
    2723== Examples
    2824
    29 It is necessary to set up a configuration for the InterTrac facility.
    30 This configuration has to be done in the TracIni file, `[intertrac]` section, for example:
     25The only prefix defined by default is `trac`, which points to trac.edgewall.org. Additional prefixes can be specified in the [TracIni#intertrac-section intertrac] section of TracIni. For example:
    3126
    3227{{{#!ini
     
    3631
    3732# -- Link to an external Trac:
    38 trac.title = Edgewall's Trac for Trac
    39 trac.url = http://trac.edgewall.org
     33genshi.title = Edgewall's Trac for Genshi
     34genshi.url = http://genshi.edgewall.org
    4035}}}
    4136
    4237The `.url` is mandatory and is used for locating the other Trac.
    43 This can be a relative URL in case that Trac environment is located on the same server.
     38It can be a relative URL when the Trac environment is located on the same server.
    4439
    4540The `.title` information is used in a tooltip, ie when hovering the cursor over an InterTrac link.
    46 
    47 Finally, the `.compat` option can be used to enable or disable a ''compatibility'' mode:
    48  * If the targeted Trac is running a version below [trac:milestone:0.10 0.10] ([trac:r3526 r3526] to be precise), then it doesn't know how to dispatch an InterTrac link, and it is up to the local Trac to prepare the correct link. Not all links will work that way, but the most common ones do. This is called the compatibility mode, and is `false` by default.
    49  * If you know that the remote Trac knows how to dispatch InterTrac links, you can explicitly disable this compatibility mode and then ''any'' TracLinks can become an InterTrac link.
    5041
    5142Now, given the above configuration, one could create the following links:
     
    5344   * `trac:wiki:InterTrac` trac:wiki:InterTrac
    5445   * `t:wiki:InterTrac` t:wiki:InterTrac
     46   * `genshi:InterTrac` genshi:InterTrac
    5547   * Keys are case insensitive: `T:wiki:InterTrac` T:wiki:InterTrac
    5648 * to the ticket #234:
    5749   * `trac:ticket:234` trac:ticket:234
    58    * `trac:#234` trac:#234
     50   * `trac:#234` trac:#234
     51   * `genshi:#234` genshi:#234
    5952   * `#T234` #T234
    6053 * to the changeset [1912]:
    6154   * `trac:changeset:1912` trac:changeset:1912
    6255   * `[T1912]` [T1912]
    63  * to the log range [3300:3330]: '''Note''': the following ones need `trac.compat=false`:
    64    * `trac:log:@3300:3330` trac:log:@3300:3330 
    65    * `[trac 3300:3330]` [trac 3300:3330] 
    66  * finally, to link to the start page of a remote Trac, simply use its prefix followed by a colon `:` and inside an explicit link. Example: `[th: Trac Hacks]`. Since Trac 0.11, note that the ''remote'' Trac has to run at least version 0.11 for this to work.
     56 * to the log range [3300:3330]:
     57   * `trac:log:@3300:3330` trac:log:@3300:3330
     58   * `[trac 3300:3330]` [trac 3300:3330]
     59   * finally, to link to the start page of a remote trac, simply use its prefix followed by ':', inside an explicit link. Example: `[th: Trac Hacks]` (note that the ''remote'' Trac has to run Trac >= 0.11 for this to work'')
    6760
    68 The generic form `intertrac_prefix:module:id` is translated to the corresponding URL `<remote>/module/id`, shorthand links are specific to some modules (e.g. !#T234 is processed by the ticket module) and for the rest (`intertrac_prefix:something`), we rely on the TracSearch#quickjump facility of the remote Trac.
     61The generic form `intertrac_prefix:module:id` is translated to the corresponding URL `<remote>/module/id`. Shorthand links are specific to some modules (e.g. !#T234 is processed by the ticket module). For the rest (`intertrac_prefix:something`), we rely on the [TracSearch#quickjump quick jump] facility of the remote Trac.
     62
     63== List of Active InterTrac Prefixes
     64
     65The following InterTrac prefixes are available on this site:
     66
     67[[InterTrac]]
    6968
    7069----