Print

Print


If the server can run php, it can run dokuwiki. No sql r other weirdness 
is needed.


Keith Gaughan wrote:
> Fabian wrote:
> 
>> What spam controls does that site have? Ive been using dokuwiki as my 
>> wiki engine. It has some excellent antispam measures. I would use 
>> mediawiki (the only other one Ive seriously considered), but it doesnt 
>> allow for secret pages, and it requirtes an sql database, which i dont 
>> have.
> 
> 
> I'm not sure how useful it'd be to you. It was written in ColdFusion as
> that's all that runs on the server my site is on.
> 
> The antispam measure used on it is one called StableCopy, which I
> borrowed from another wiki engine called PeriPeri[1]. I've seen it
> elsewhere since and it provides a good balance between keeping out spam
> and flame wars, and keeping the barrier to entry as low as possible.
> 
> The way it works is that each page comes in two versions, the stable 
> version and the edit version. People who are editing the page edit the
> its edit version, but if you're just looking at the site, what you see
> is the stable version. If people stop making modifications to the edit
> version for some period of some, say a day, the edit version is said to
> have become stable, so it replaces the old stable version of the page.
> 
> Mind you, the code is file based. It wouldn't be terribly hard to
> convert it to PHP if you'd like. The part of it that *really* needs work
> is the formatter, which owing to a combination of bugs in ColdFusion 5's
> regex engine and my own laziness, isn't as good as it ought to be.
> 
> K.
> 
> [1] http://www.srcf.ucam.org/~cjp39/Peri/PeriPeri
> 
>