Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Small tweak to the advice for "reader" category capability for forums |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
ea67aadeee78ede48dee8a66a5e256fa |
| User & Date: | wyoung 2018-08-08 19:25:09 |
Context
|
2018-08-08
| ||
| 19:30 | More tweaks to the forum.wiki doc (check-in: 5d75504a user: wyoung tags: trunk) | |
| 19:25 | Small tweak to the advice for "reader" category capability for forums (check-in: ea67aade user: wyoung tags: trunk) | |
| 19:22 | Added the "Skin Setup" section to the new forum.wiki document (check-in: 3ec8f0a9 user: wyoung tags: trunk) | |
Changes
Changes to www/forum.wiki.
103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 |
For public Fossil repositories that wish to accept new users without involving a human, go into Admin → Access and enable the "Allow users to register themselves" setting. You may also wish to give the <tt>anonymous</tt> user category the Read Forum (2) and Write Forum (3) capabilities: this allows people to post without creating an account simply by solving [./antibot.wiki | a simple CAPTCHA]. For a private repository, you will likely wish to give the "23" capability pair to the <tt>reader</tt> user category instead. For either type of repository, you are likely to want to give at least the Write Trusted (4) capability to the <tt>developer</tt> user category. By following this advice, you should not need to tediously add capabilities to individual accounts, except in atypical cases, such as |
| > | |
103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 |
For public Fossil repositories that wish to accept new users without involving a human, go into Admin → Access and enable the "Allow users to register themselves" setting. You may also wish to give the <tt>anonymous</tt> user category the Read Forum (2) and Write Forum (3) capabilities: this allows people to post without creating an account simply by solving [./antibot.wiki | a simple CAPTCHA]. For a private repository, you probably won't want to give the <tt>anonymous</tt> user any forum access, but you may wish to give capability "2" to the <tt>reader</tt> user category. For either type of repository, you are likely to want to give at least the Write Trusted (4) capability to the <tt>developer</tt> user category. By following this advice, you should not need to tediously add capabilities to individual accounts, except in atypical cases, such as |