Merge branch 'master' of ssh://git.ikiwiki.info/srv/git/ikiwiki.info

master
Joey Hess 2009-05-05 13:57:00 -04:00
commit 72736b5e72
2 changed files with 69 additions and 0 deletions

View File

@ -165,3 +165,48 @@ I setup ikiwiki on a fedora 10 machine and I am using apache as my http server.
> ikiwiki respects the umask, so if your umask is one that causes things to > ikiwiki respects the umask, so if your umask is one that causes things to
> be group writable, they will by. If you want to override that, there is > be group writable, they will by. If you want to override that, there is
> also a `umask ` setting in your setup file. --[[Joey]] > also a `umask ` setting in your setup file. --[[Joey]]
----
/etc/ikiwiki/auto.setup tries to get abs_path of a non-existent "repository" path (in ikiwiki-makerepo), and that doesn't work in my perl:
<pre>
[mort@localhost ~]$ perl -e 'use Cwd q{abs_path}; print abs_path("/var")'
/var[mort@localhost ~]$ perl -e 'use Cwd q{abs_path}; print abs_path("/abcde")'
[mort@localhost ~]$
</pre>
Because of this, /etc/ikiwiki/auto.setup fails:
<pre>
$ ikiwiki -setup /etc/ikiwiki/auto.setup
What will the wiki be named? wiki
What revision control system to use? git
What wiki user (or openid) will be admin? mort
Setting up wiki ...
internal error finding repository abs_path
/etc/ikiwiki/auto.setup: failed to set up the repository with ikiwiki-makerepo
usage: ikiwiki [options] source dest
ikiwiki --setup configfile
$ perl -v
This is perl, v5.8.8 built for i386-linux-thread-multi
(with 2 registered patches, see perl -V for more detail)
Copyright 1987-2007, Larry Wall
Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.
Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.
$
</pre>
Can't ikiwiki's "make test" perhaps test for this, so that one knows something will go wrong?
-- Ivan Z.

View File

@ -0,0 +1,24 @@
The [[blogspam plugin|plugins/blogspam]] is just great.
However, it lacks support in the web interface to [train comments as
SPAM](http://blogspam.net/api/classifyComment.html), when they were
erroneously identified as ham. It would be great to have such
support, also in the spirit of helping
[blogspam.net](http://blogspam.net) to get better and better.
What would consist the most appropriate user interface is not entirely
clear to me in the general case (wiki page editing). The case of blog
comments look easier to: when the admin user is logged in (and if the
blogspam plugin is enabled), each comment can have an extra link "mark
as SPAM" which would both delete/revert the comment and submit it to
the configured blogspam server for training.
Similarly, ham training can be plugged directly into the current
comment moderation interface. Each comment that gets approved by the
admin, can be sent to blogspam.net as ham. If this is considered too
"aggressive", this behaviour can need to be explicitly enabled by
turning on a configuration option.
-- [[Zack]]
[[!tag wishlist]]