138 | | [../Sibling see next sibling] or [[../Sibling|see next sibling]] |
139 | | |
140 | | ''(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. |
| 138 | [../Sibling see next sibling] or [[../Sibling|see next sibling]] |
| 139 | |
| 140 | But in practice you often won't need to add the `../` prefix to link to a sibling page. |
| 141 | For resolving the location of a wiki link, it's the target page closest in the hierarchy |
| 142 | to the page where the link is written which will be selected. So for example, within |
| 143 | a sub-hierarchy, a sibling page will be targeted in preference to a toplevel page. |
| 144 | This makes it easy to copy or move pages to a sub-hierarchy by [[WikiNewPage#renaming|renaming]] without having to adapt the links. |
| 145 | |
| 146 | In order to link explicitly to a [=#toplevel toplevel] Wiki page, |
| 147 | use the `wiki:/` prefix. |
| 148 | Be careful **not** to use the `/` prefix alone, as this corresponds to the |
| 149 | [#Server-relativelinks] syntax and with such a link you will lack the `/wiki/` |
| 150 | part in the resulting URL. |
| 151 | |
| 152 | ''(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 since 0.11, such a link will stay in the wiki namespace and therefore link to a sibling page. |
| 153 | See [#Server-relativelinks] for the new syntax. |