Fossil SCM
Fixed some Markdown-isms just checked into www/forum.wiki.
Commit
34a3bc12b0a699de7bdfb62a580ea8f6a0ef6884980f96f7512975749d830bc5
Parent
04d4bde1706ea24…
1 file changed
+21
-20
+21
-20
| --- www/forum.wiki | ||
| +++ www/forum.wiki | ||
| @@ -201,18 +201,20 @@ | ||
| 201 | 201 | configurations. |
| 202 | 202 | |
| 203 | 203 | If you have an existing repository, you have two choices if you want its |
| 204 | 204 | skin to be upgraded to support forums: |
| 205 | 205 | |
| 206 | -1. Go into Admin → Skins and switch from your current skin to one | |
| 207 | - of the stock skins. If you were on a stock skin, just switch away | |
| 208 | - from your current one to the actual stock skin, since they will be | |
| 209 | - different after the upgrade. | |
| 210 | - | |
| 211 | -2. If you have local customization that you do not want to throw away, | |
| 212 | - you can use the diff feature of Fossil's skin editor to show how the | |
| 213 | - skins differ. | |
| 206 | +<ol> | |
| 207 | + <li>Go into Admin → Skins and switch from your current skin to | |
| 208 | + one of the stock skins. If you were on a stock skin, just switch away | |
| 209 | + from your current one to the actual stock skin, since they will be | |
| 210 | + different after the upgrade.</li> | |
| 211 | + | |
| 212 | + <li>If you have local customization that you do not want to throw | |
| 213 | + away, you can use the diff feature of Fossil's skin editor to show how | |
| 214 | + the skins differ.</li> | |
| 215 | +</ol> | |
| 214 | 216 | |
| 215 | 217 | The remainder of this section summarizes the differences you're expected |
| 216 | 218 | to see when taking option #2. |
| 217 | 219 | |
| 218 | 220 | The first thing is that you'll need to add something like the following |
| @@ -266,25 +268,24 @@ | ||
| 266 | 268 | color: #6A7F94; |
| 267 | 269 | } |
| 268 | 270 | </verbatim> |
| 269 | 271 | |
| 270 | 272 | This changes the clicked-hyperlink color for the forum post links on the |
| 271 | -main `/forum` page only, which allows your browser's history mechanism | |
| 272 | -to show which threads a user has read and which not. The link color will | |
| 273 | -change back to the normal link color — indicating "unread" — when a | |
| 274 | -reply is added to an existing thread because that changes where the link | |
| 275 | -from the `/forum` page points, taking you to the newest post in the | |
| 276 | -thread. | |
| 273 | +main <tt>/forum</tt> page only, which allows your browser's history | |
| 274 | +mechanism to show which threads a user has read and which not. The link | |
| 275 | +color will change back to the normal link color — indicating "unread" — | |
| 276 | +when a reply is added to an existing thread because that changes where | |
| 277 | +the link from the <tt>/forum</tt> page points, taking you to the newest | |
| 278 | +post in the thread. | |
| 277 | 279 | |
| 278 | 280 | The color given above is suitable for the stock skin. |
| 279 | 281 | |
| 280 | -Beware that when changing this example, there are some [stringent | |
| 281 | -restrictions][vpriv] in modern browsers to prevent snoopy web sites from | |
| 282 | -brute-forcing your browsing history. (See the link for the method, which | |
| 283 | -explains the restrictions.) | |
| 284 | - | |
| 285 | -[vpriv]: https://hacks.mozilla.org/2010/03/privacy-related-changes-coming-to-css-vistited/ | |
| 282 | +Beware that when changing this example, there are some | |
| 283 | +[https://hacks.mozilla.org/2010/03/privacy-related-changes-coming-to-css-vistited/ | |
| 284 | +| stringent restrictions] in modern browsers to prevent snoopy web sites | |
| 285 | +from brute-forcing your browsing history. (See the link for the method, | |
| 286 | +which explains the restrictions.) | |
| 286 | 287 | |
| 287 | 288 | |
| 288 | 289 | <h3 id="search">Enable Forum Search</h3> |
| 289 | 290 | |
| 290 | 291 | One of the underlying assumptions of the forum feature is that you will |
| 291 | 292 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -201,18 +201,20 @@ | |
| 201 | configurations. |
| 202 | |
| 203 | If you have an existing repository, you have two choices if you want its |
| 204 | skin to be upgraded to support forums: |
| 205 | |
| 206 | 1. Go into Admin → Skins and switch from your current skin to one |
| 207 | of the stock skins. If you were on a stock skin, just switch away |
| 208 | from your current one to the actual stock skin, since they will be |
| 209 | different after the upgrade. |
| 210 | |
| 211 | 2. If you have local customization that you do not want to throw away, |
| 212 | you can use the diff feature of Fossil's skin editor to show how the |
| 213 | skins differ. |
| 214 | |
| 215 | The remainder of this section summarizes the differences you're expected |
| 216 | to see when taking option #2. |
| 217 | |
| 218 | The first thing is that you'll need to add something like the following |
| @@ -266,25 +268,24 @@ | |
| 266 | color: #6A7F94; |
| 267 | } |
| 268 | </verbatim> |
| 269 | |
| 270 | This changes the clicked-hyperlink color for the forum post links on the |
| 271 | main `/forum` page only, which allows your browser's history mechanism |
| 272 | to show which threads a user has read and which not. The link color will |
| 273 | change back to the normal link color — indicating "unread" — when a |
| 274 | reply is added to an existing thread because that changes where the link |
| 275 | from the `/forum` page points, taking you to the newest post in the |
| 276 | thread. |
| 277 | |
| 278 | The color given above is suitable for the stock skin. |
| 279 | |
| 280 | Beware that when changing this example, there are some [stringent |
| 281 | restrictions][vpriv] in modern browsers to prevent snoopy web sites from |
| 282 | brute-forcing your browsing history. (See the link for the method, which |
| 283 | explains the restrictions.) |
| 284 | |
| 285 | [vpriv]: https://hacks.mozilla.org/2010/03/privacy-related-changes-coming-to-css-vistited/ |
| 286 | |
| 287 | |
| 288 | <h3 id="search">Enable Forum Search</h3> |
| 289 | |
| 290 | One of the underlying assumptions of the forum feature is that you will |
| 291 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -201,18 +201,20 @@ | |
| 201 | configurations. |
| 202 | |
| 203 | If you have an existing repository, you have two choices if you want its |
| 204 | skin to be upgraded to support forums: |
| 205 | |
| 206 | <ol> |
| 207 | <li>Go into Admin → Skins and switch from your current skin to |
| 208 | one of the stock skins. If you were on a stock skin, just switch away |
| 209 | from your current one to the actual stock skin, since they will be |
| 210 | different after the upgrade.</li> |
| 211 | |
| 212 | <li>If you have local customization that you do not want to throw |
| 213 | away, you can use the diff feature of Fossil's skin editor to show how |
| 214 | the skins differ.</li> |
| 215 | </ol> |
| 216 | |
| 217 | The remainder of this section summarizes the differences you're expected |
| 218 | to see when taking option #2. |
| 219 | |
| 220 | The first thing is that you'll need to add something like the following |
| @@ -266,25 +268,24 @@ | |
| 268 | color: #6A7F94; |
| 269 | } |
| 270 | </verbatim> |
| 271 | |
| 272 | This changes the clicked-hyperlink color for the forum post links on the |
| 273 | main <tt>/forum</tt> page only, which allows your browser's history |
| 274 | mechanism to show which threads a user has read and which not. The link |
| 275 | color will change back to the normal link color — indicating "unread" — |
| 276 | when a reply is added to an existing thread because that changes where |
| 277 | the link from the <tt>/forum</tt> page points, taking you to the newest |
| 278 | post in the thread. |
| 279 | |
| 280 | The color given above is suitable for the stock skin. |
| 281 | |
| 282 | Beware that when changing this example, there are some |
| 283 | [https://hacks.mozilla.org/2010/03/privacy-related-changes-coming-to-css-vistited/ |
| 284 | | stringent restrictions] in modern browsers to prevent snoopy web sites |
| 285 | from brute-forcing your browsing history. (See the link for the method, |
| 286 | which explains the restrictions.) |
| 287 | |
| 288 | |
| 289 | <h3 id="search">Enable Forum Search</h3> |
| 290 | |
| 291 | One of the underlying assumptions of the forum feature is that you will |
| 292 |