Fossil

Check-in [420d6e77e4]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Adjust forum-closure docs to match the previous check-in.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 420d6e77e48e2140e10e5fe715a346c395d6ffabbbe7a47a8c5e7dc9e96c0b90
User & Date: stephan 2023-06-10 19:12:42.582
Context
2023-06-12
08:53
Add a CSRF check for the forum post Close/Re-open button. check-in: 619d51440f user: stephan tags: trunk
2023-06-10
19:12
Adjust forum-closure docs to match the previous check-in. check-in: 420d6e77e4 user: stephan tags: trunk
19:03
Remove the superfluous Close Post option from the forum edit page. check-in: b2f007178a user: stephan tags: trunk
Changes
Unified Diff Ignore Whitespace Patch
Changes to www/forum.wiki.
391
392
393
394
395
396
397
398
399
400
401

402
403
404
405
406
407
408
409
410
411

Note that closing a post is effectively an "advisory lock" and may be
bypassed. Any user, admin or otherwise, who can push changes to a
repository may bypass closure of a post by setting the appropriate
artifact tags on a local copy and pushing those changes to a remote
copy of the forum.

Closing may be achieved in two ways:

  *  When a given post is selected in the web interface, a "Close" or
     "Re-open" button will appear under the post if the user has

     permissions to perform that operation.
  *  A Close option is added at the bottom of the Edit page, permissions
     permitting.

Though forum users are permitted to delete their own posts, they are
not permitted, without appropriate permissions, to close their own
posts. This is intentional, as closing one's own post can be used to
antagonize other forum-goers. For example, by posting something
trollish or highly contraversial in nature and closing the post to
further responses.







<
|
|
|
>
|
|
|




|


391
392
393
394
395
396
397

398
399
400
401
402
403
404
405
406
407
408
409
410
411

Note that closing a post is effectively an "advisory lock" and may be
bypassed. Any user, admin or otherwise, who can push changes to a
repository may bypass closure of a post by setting the appropriate
artifact tags on a local copy and pushing those changes to a remote
copy of the forum.


The option to close a post, permissions permitting, appears as a
"Close" button on the currently-selected post. If the selected post is
alread closed, a "Re-open" button will be shown instead. In order to
re-open a post, <em>the closed post itself</em> must be
selected. Selecting a response to that post, which is implicitly
closed by the closure of its parent, will <em>not</em> offer a re-open
option.

Though forum users are permitted to delete their own posts, they are
not permitted, without appropriate permissions, to close their own
posts. This is intentional, as closing one's own post can be used to
antagonize other forum users. For example, by posting something
trollish or highly contraversial in nature and closing the post to
further responses.