Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Clarity fixes to the Email Alerts capability paragraph of forum.wiki |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
d6e5754d71b8b8c469189a2eb313de7f |
| User & Date: | wyoung 2018-08-29 03:13:53 |
Context
|
2018-08-29
| ||
| 03:25 | Assorted improvements to the "Skin Setup" section of forum.wiki. check-in: 04d4bde1 user: wyoung tags: trunk | |
| 03:13 | Clarity fixes to the Email Alerts capability paragraph of forum.wiki check-in: d6e5754d user: wyoung tags: trunk | |
|
2018-08-27
| ||
| 15:00 | Remove unnecessary execute bit check-in: cabc447c user: andygoth tags: trunk | |
Changes
Changes to www/forum.wiki.
171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 |
For either type of repository, you are likely to want to give at least the WriteTrusted capability (4) to users in the <tt>developer</tt> category. If you did not give the Read Forum capability (2) to <tt>anonymous</tt> above, you should give <tt>developer</tt> that capability here if you choose to give it capability 3 or 4. You must give at least one user or user category the Email Alerts capability (7), else the only people able to sign themselves up for email notifications are those with the Setup or Admin capability. Those users could sign others up via Admin → Notification, but you probably want to give this capability to one of the user categories. Give it to <tt>nobody</tt> if you want anyone to sign up without any restrictions. Give it to <tt>anonymous</tt> if you want the user to solve a simple CAPTCHA before signing up. Give it to <tt>reader</tt> or <tt>developer</tt> if you want only users with Fossil logins to have this ability. (That's assuming you give one or both of these capabilities to every user on your Fossil repository.) By following this advice, you should not need to tediously add capabilities to individual accounts except in atypical cases, such as to grant the Moderate Forum capability (5) to an uncommonly highly-trusted user. |
| | | | | > | | | | | | |
171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 |
For either type of repository, you are likely to want to give at least the WriteTrusted capability (4) to users in the <tt>developer</tt> category. If you did not give the Read Forum capability (2) to <tt>anonymous</tt> above, you should give <tt>developer</tt> that capability here if you choose to give it capability 3 or 4. If you want to use the email notification feature, by default only those users in the Setup and Admin user categories can make use of it. Grant the Email Alerts capability (7) to give others access to this feature. Alternately, you can handle notification signups outside of Fossil, with a Setup or Admin users manually signing users up via Admin → Notification. You'll want to grant this capability to the <tt>nobody</tt> user category if you want anyone to sign up without any restrictions. Give it to <tt>anonymous</tt> instead if you want the user to solve a simple CAPTCHA before signing up. Or, give it to <tt>reader</tt> or <tt>developer</tt> if you want only users with Fossil logins to have this ability. (That's assuming you give one or both of these capabilities to every user on your Fossil repository.) By following this advice, you should not need to tediously add capabilities to individual accounts except in atypical cases, such as to grant the Moderate Forum capability (5) to an uncommonly highly-trusted user. |