- Dec 21, 2016, 10:38:27 AM (4 years ago)
v7 v8 45 45 The `.title` information is used in a tooltip, ie when hovering the cursor over an InterTrac link. 46 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 51 47 Now, given the above configuration, one could create the following links: 52 48 * to this InterTrac page: … … 61 57 * `trac:changeset:1912` trac:changeset:1912 62 58 * `[T1912]` [T1912] 63 * to the log range [3300:3330]: '''Note''': the following ones need `trac.compat=false`: 59 * to the log range [3300:3330]: 64 60 * `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. 61 * `[trac 3300:3330]` [trac 3300:3330] 62 67 63 68 64 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.