From 16aad6825d2cdae2c1e06604f9d5652d376fca18 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlY5yDefnXSHvWGbJ9kvhnAyQZiAAttENk" Date: Tue, 14 Sep 2010 17:04:14 +0000 Subject: [PATCH 1/2] corrected link --- doc/tips/vim_and_ikiwiki.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/tips/vim_and_ikiwiki.mdwn b/doc/tips/vim_and_ikiwiki.mdwn index eb22e353a..e4136aa5d 100644 --- a/doc/tips/vim_and_ikiwiki.mdwn +++ b/doc/tips/vim_and_ikiwiki.mdwn @@ -9,7 +9,7 @@ directives and wikilinks. It only supports prefixed directives, i.e., ------ -The previous syntax definition for ikiwiki links is at [[ikiwiki.vim]]; however, +The previous syntax definition for ikiwiki links is at [[vim_syntax_highlighting/ikiwiki.vim]]; however, it seems to not be [[maintained anymore|forum/navigation_of_wiki_pages_on_local_filesystem_with_vim#syn-maintenance]], and it has some [[issues|forum/ikiwiki_vim_syntaxfile]]. From 382b0b349988d92f8571b38beb8be003e0b334a0 Mon Sep 17 00:00:00 2001 From: "http://k1024.org/~iusty/" Date: Tue, 14 Sep 2010 18:33:15 +0000 Subject: [PATCH 2/2] Add new bug about the comments/blogspam plugins --- ...spam_plugin_not_allowing_non-ASCII_chars__63__.mdwn | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/blog_spam_plugin_not_allowing_non-ASCII_chars__63__.mdwn diff --git a/doc/bugs/blog_spam_plugin_not_allowing_non-ASCII_chars__63__.mdwn b/doc/bugs/blog_spam_plugin_not_allowing_non-ASCII_chars__63__.mdwn new file mode 100644 index 000000000..22242a97f --- /dev/null +++ b/doc/bugs/blog_spam_plugin_not_allowing_non-ASCII_chars__63__.mdwn @@ -0,0 +1,10 @@ +Hi, + +I'm trying to add a comment, and ikiwiki fails with this error message: + + Error: HTTP::Message content must be bytes at /usr/share/perl5/RPC/XML/Client.pm line 308 + +This seems to happen because I had a non-ASCII character in the comment (an ellipse, …). +The interesting part is that the comment preview works fine, just the save fails. Probably +this means that the blogspam plugin is the culprit (hence the error in RPC::XML::Client library). +I'm using version 3.20100815~bpo50+. Thanks!