Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fixed some Markdown-isms just checked into www/forum.wiki. |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
34a3bc12b0a699de7bdfb62a580ea8f6 |
| User & Date: | wyoung 2018-08-29 03:31:04.780 |
Context
|
2018-08-29
| ||
| 11:04 | Try to start a new write transaction before updating the VCACHE table. This will hopefully prevent occasional "database is locked" errors when browsing the documentation. ... (check-in: 03979823 user: drh tags: trunk) | |
| 03:31 | Fixed some Markdown-isms just checked into www/forum.wiki. ... (check-in: 34a3bc12 user: wyoung tags: trunk) | |
| 03:25 | Assorted improvements to the "Skin Setup" section of forum.wiki. ... (check-in: 04d4bde1 user: wyoung tags: trunk) | |
Changes
Changes to www/forum.wiki.
| ︙ | ︙ | |||
199 200 201 202 203 204 205 | If you create a new Fossil repository with version 2.7 or newer, its default skin is already set up correctly for typical forum configurations. If you have an existing repository, you have two choices if you want its skin to be upgraded to support forums: | > | | | | | | | > | 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 | If you create a new Fossil repository with version 2.7 or newer, its default skin is already set up correctly for typical forum configurations. If you have an existing repository, you have two choices if you want its skin to be upgraded to support forums: <ol> <li>Go into Admin → Skins and switch from your current skin to one of the stock skins. If you were on a stock skin, just switch away from your current one to the actual stock skin, since they will be different after the upgrade.</li> <li>If you have local customization that you do not want to throw away, you can use the diff feature of Fossil's skin editor to show how the skins differ.</li> </ol> The remainder of this section summarizes the differences you're expected to see when taking option #2. The first thing is that you'll need to add something like the following to the Header part of the skin to create the navbar link: |
| ︙ | ︙ | |||
264 265 266 267 268 269 270 |
<verbatim>
div.forumPosts a:visited {
color: #6A7F94;
}
</verbatim>
This changes the clicked-hyperlink color for the forum post links on the
| | | | | | | | > | | | < < | 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 |
<verbatim>
div.forumPosts a:visited {
color: #6A7F94;
}
</verbatim>
This changes the clicked-hyperlink color for the forum post links on the
main <tt>/forum</tt> page only, which allows your browser's history
mechanism to show which threads a user has read and which not. The link
color will change back to the normal link color — indicating "unread" —
when a reply is added to an existing thread because that changes where
the link from the <tt>/forum</tt> page points, taking you to the newest
post in the thread.
The color given above is suitable for the stock skin.
Beware that when changing this example, there are some
[https://hacks.mozilla.org/2010/03/privacy-related-changes-coming-to-css-vistited/
| stringent restrictions] in modern browsers to prevent snoopy web sites
from brute-forcing your browsing history. (See the link for the method,
which explains the restrictions.)
<h3 id="search">Enable Forum Search</h3>
One of the underlying assumptions of the forum feature is that you will
want to be able to search the forum archives, so the <tt>/forum</tt>
page always includes a search box. Since that depends on search being
|
| ︙ | ︙ |