Changes between Version 1 and Version 2 of InterTrac
- Timestamp:
- 2010-06-14 04:25:44 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
InterTrac
v1 v2 29 29 The aliases are defined in `trac.ini` (see below). 30 30 The prefix is case insensitive. 31 32 When a TracLink is enclosed in brackets, the alias is expanded. That is, `[th:ticket:1]` is displayed as `trachacks:ticket:1`, since `th` is an alias for `trachacks`. If the TracLink is not enclosed in brackets, then the alias is displayed as it is typed. 31 33 32 34 For convenience, there's also some alternative short-hand form, … … 61 63 Finally, the `.compat` option can be used to activate or disable 62 64 a ''compatibility'' mode: 63 * If the targeted Trac is running a version below milestone:0.1064 ( r3526to be precise), then it doesn't know how to dispatch an InterTrac65 * If the targeted Trac is running a version below [trac:milestone:0.10 0.10] 66 ([trac:r3526 r3526] to be precise), then it doesn't know how to dispatch an InterTrac 65 67 link, and it's up to the local Trac to prepare the correct link. 66 68 Not all links will work that way, but the most common do. 67 69 This is called the compatibility mode, and is `true` by default. 68 70 * If you know that the remote Trac knows how to dispatch InterTrac links, 69 you can explicit ely disable this compatibility mode and then ''any''71 you can explicitly disable this compatibility mode and then ''any'' 70 72 TracLinks can become an InterTrac link. 71 73