Differences From Artifact [c8e96dbccd]:
- File
www/shunning.wiki
— part of check-in
[1fd407f61a]
at
2023-05-10 17:02:02
on branch trunk
— In an effort to make www/* source documents read as cleanly as their
rendered counterparts, replaced nearly all use of HTML "p" tags, relying
instead on the Wiki and Markdown markup features to achieve the same
appearance. The only uses remaining are:
- in Markdown nested lists, where blank lines should render the list items as separate paragraphs just as at the list's top level; since it does not, if you want a line break, you either have to wrap the item in "p" tags or do the double-br hack.
- in Wiki where blank lines within a list give you a separate list in the HTML output; this is fine for bullet lists, but with numbered lists it causes the numbering to restart unless you do the same sort of manual HTML workaround as with the prior item
- in plain HTML docs and wiki docs between "nowiki" tags
In many places, this cleanup gets rid of pointless stray "p" tags, placating HTML verifiers. (user: wyoung size: 7902) [more...]
To Artifact [2945acf2d1]:
- File www/shunning.wiki — part of check-in [8e9fc86018] at 2024-10-23 09:16:51 on branch bv-corrections01 — Changes for the following files under www/: settings.wiki shunning.wiki stats.wiki style.wiki sync.wiki (user: brickviking size: 7902) [more...]
| ︙ | ︙ | |||
31 32 33 34 35 36 37 | <h2>Alternatives</h2> All of these are rare cases: Fossil is [./antibot.wiki | designed to foil spammers up front], legally problematic check-ins should range from rare to nonexistent, and you have to go way out of your way to force Fossil to insert bad control artifacts. Therefore, before we get to | | | 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 |
<h2>Alternatives</h2>
All of these are rare cases: Fossil is [./antibot.wiki | designed to
foil spammers up front], legally problematic check-ins should range from
rare to nonexistent, and you have to go way out of your way to force
Fossil to insert bad control artifacts. Therefore, before we get to
methods of permanently deleting content from a Fossil repo, let's give
some alternatives that usually suffice, which don't damage the project's
fossil record:
* When a forum post or wiki article is "deleted," what actually
happens is that a new empty version is added to the Fossil repository.
The web interface interprets this
as "deleted," but the prior version remains available if you go
|
| ︙ | ︙ | |||
131 132 133 134 135 136 137 |
by the normal "sync" mechanism,
but it is still possible to copy shuns from one repository to another
using the "configuration" command:
<b>fossil configuration pull shun</b> <i>remote-url</i><br>
<b>fossil configuration push shun</b> <i>remote-url</i>
| | | 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 |
by the normal "sync" mechanism,
but it is still possible to copy shuns from one repository to another
using the "configuration" command:
<b>fossil configuration pull shun</b> <i>remote-url</i><br>
<b>fossil configuration push shun</b> <i>remote-url</i>
The two commands above will pull or push shunning lists from or to
the <i>remote-url</i> indicated and merge the lists on the receiving
end. "Admin" privilege on the remote server is required in order to
push a shun list. In contrast, the shunning list will be automatically
received by default as part of a normal client "pull" operation unless
disabled by the "<tt>auto-shun</tt>" setting.
Note that the shunning list remains in the repository even after the
|
| ︙ | ︙ |