Fossil SCM
Added the "Skin Setup" section to the new forum.wiki document
Commit
3ec8f0a960649064d8d90087769904e5493a8733dfd27d08056bd92e49869930
Parent
dd0a2dd3d3bb849…
1 file changed
+25
+25
| --- www/forum.wiki | ||
| +++ www/forum.wiki | ||
| @@ -117,10 +117,35 @@ | ||
| 117 | 117 | By following this advice, you should not need to tediously add |
| 118 | 118 | capabilities to individual accounts, except in atypical cases, such as |
| 119 | 119 | to grant the Moderate Forum capability (5) to an uncommonly |
| 120 | 120 | highly-trusted user. |
| 121 | 121 | |
| 122 | + | |
| 123 | +<h3>Skin Setup</h3> | |
| 124 | + | |
| 125 | +If you create a new Fossil repository with version 2.7 or newer, its | |
| 126 | +default skin is already set up correctly for typical forum | |
| 127 | +configurations. | |
| 128 | + | |
| 129 | +Those upgrading existing repositories will need to edit the Header part | |
| 130 | +of their existing Fossil skin in Admin → Skins, adding something | |
| 131 | +like this to create the navbar link: | |
| 132 | + | |
| 133 | +<verbatim> | |
| 134 | + if {[anycap 23456] || [anoncap 2] || [anoncap 3]} { | |
| 135 | + menulink /forum Forum | |
| 136 | + } | |
| 137 | +</verbatim> | |
| 138 | + | |
| 139 | +These rules say that any logged-in user with any forum-related | |
| 140 | +capability (2-6 inclusive, as of this writing) or an anonymous user with | |
| 141 | +read or write capability on the forum (2, 3) will see the "Forum" navbar | |
| 142 | +link, which just takes you to <tt>/forum</tt>. | |
| 143 | + | |
| 144 | +The exact code you need here varies depending on which skin you're | |
| 145 | +using. Follow the style you see for the other navbar links. | |
| 146 | + | |
| 122 | 147 | |
| 123 | 148 | <h3>Single Sign-On</h3> |
| 124 | 149 | |
| 125 | 150 | If you choose to host your discussion forums within the same repository |
| 126 | 151 | as your project's other Fossil-managed content, you inherently have a |
| 127 | 152 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -117,10 +117,35 @@ | |
| 117 | By following this advice, you should not need to tediously add |
| 118 | capabilities to individual accounts, except in atypical cases, such as |
| 119 | to grant the Moderate Forum capability (5) to an uncommonly |
| 120 | highly-trusted user. |
| 121 | |
| 122 | |
| 123 | <h3>Single Sign-On</h3> |
| 124 | |
| 125 | If you choose to host your discussion forums within the same repository |
| 126 | as your project's other Fossil-managed content, you inherently have a |
| 127 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -117,10 +117,35 @@ | |
| 117 | By following this advice, you should not need to tediously add |
| 118 | capabilities to individual accounts, except in atypical cases, such as |
| 119 | to grant the Moderate Forum capability (5) to an uncommonly |
| 120 | highly-trusted user. |
| 121 | |
| 122 | |
| 123 | <h3>Skin Setup</h3> |
| 124 | |
| 125 | If you create a new Fossil repository with version 2.7 or newer, its |
| 126 | default skin is already set up correctly for typical forum |
| 127 | configurations. |
| 128 | |
| 129 | Those upgrading existing repositories will need to edit the Header part |
| 130 | of their existing Fossil skin in Admin → Skins, adding something |
| 131 | like this to create the navbar link: |
| 132 | |
| 133 | <verbatim> |
| 134 | if {[anycap 23456] || [anoncap 2] || [anoncap 3]} { |
| 135 | menulink /forum Forum |
| 136 | } |
| 137 | </verbatim> |
| 138 | |
| 139 | These rules say that any logged-in user with any forum-related |
| 140 | capability (2-6 inclusive, as of this writing) or an anonymous user with |
| 141 | read or write capability on the forum (2, 3) will see the "Forum" navbar |
| 142 | link, which just takes you to <tt>/forum</tt>. |
| 143 | |
| 144 | The exact code you need here varies depending on which skin you're |
| 145 | using. Follow the style you see for the other navbar links. |
| 146 | |
| 147 | |
| 148 | <h3>Single Sign-On</h3> |
| 149 | |
| 150 | If you choose to host your discussion forums within the same repository |
| 151 | as your project's other Fossil-managed content, you inherently have a |
| 152 |