Changes between Version 2 and Version 3 of InterTrac
- Timestamp:
- Aug 1, 2024, 10:29:35 AM (4 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
InterTrac
v2 v3 1 1 = InterTrac Links 2 2 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]] 3 Trac 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. 8 4 9 5 == Link Syntax … … 15 11 }}} 16 12 17 The other resource is specified using a regular TracLinks, of any flavor.13 The other resource is specified using a regular !TracLink, of any flavor. 18 14 19 That target environment name is either the real name of the environment or an alias for it.15 That target environment name is either the real name of the environment or an alias. 20 16 The aliases are defined in the `trac.ini` file, see below. 21 17 The prefix is case insensitive. 22 18 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 , iethe above would be displayed as `WikiExtrasPlugin`.19 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. For example, the above would be displayed as `WikiExtrasPlugin`. 24 20 25 For convenience, there is also an alternat ive 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]`.21 For 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]`. 26 22 27 23 == Examples 28 24 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: 25 The 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: 31 26 32 27 {{{#!ini … … 36 31 37 32 # -- Link to an external Trac: 38 trac.title = Edgewall's Trac for Trac 39 trac.url = http://trac.edgewall.org33 genshi.title = Edgewall's Trac for Genshi 34 genshi.url = http://genshi.edgewall.org 40 35 }}} 41 36 42 37 The `.url` is mandatory and is used for locating the other Trac. 43 This can be a relative URL in case thatTrac environment is located on the same server.38 It can be a relative URL when the Trac environment is located on the same server. 44 39 45 40 The `.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.50 41 51 42 Now, given the above configuration, one could create the following links: … … 53 44 * `trac:wiki:InterTrac` trac:wiki:InterTrac 54 45 * `t:wiki:InterTrac` t:wiki:InterTrac 46 * `genshi:InterTrac` genshi:InterTrac 55 47 * Keys are case insensitive: `T:wiki:InterTrac` T:wiki:InterTrac 56 48 * to the ticket #234: 57 49 * `trac:ticket:234` trac:ticket:234 58 * `trac:#234` trac:#234 50 * `trac:#234` trac:#234 51 * `genshi:#234` genshi:#234 59 52 * `#T234` #T234 60 53 * to the changeset [1912]: 61 54 * `trac:changeset:1912` trac:changeset:1912 62 55 * `[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'') 67 60 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. 61 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). 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 65 The following InterTrac prefixes are available on this site: 66 67 [[InterTrac]] 69 68 70 69 ----