> For mercurial, these run respectively `hg add` and `hg commit`. If the
> add or commit fails, it will print a warning to stderr, you might check
> apache's error.log to see if there's anything there. --[[Joey]]
+
+>>The problem was using accented characters (é, í) on the change comments. I didn't have
+>>an UTF-8 locale enabled in my setup file. By coincidence this happened for the first time
+>>in a couple of consecutive blog posts, so I was mistaken about the root of the problem. I don't know if
+>>you will consider this behavior a bug, since it's strictly speaking a misconfiguration but it
+>>still causes ikiwiki's mercurial backend to fail. A quick note in the docs might be a good idea. For my part, please
+>>close this bug, and thanks for the help. --[[buo]]
--- /dev/null
+The htmltidy plugin as in the Backports.org version 2.32.3~bpo40+1 of ikiwiki does not play well with other usages of HTML Tidy since it has no possibility to use an alternative config file.
+
+E.g. since I usually use HTML Tidy manually only to check and not to fix HTML, I have "write-back: no" in my $HOME/.tidyrc which throws an awful lot of Perl warnings and renders all ikiwiki pages empty as soon as I enable htmltidy.
+
+I see two possibilities how to fix this:
+
+1) Replace "$pid=open2(*IN, *OUT, 'tidy -quiet -asxhtml -utf8 --show-body-only yes -
+-show-warnings no --tidy-mark no');" by "$pid=open2(*IN, *OUT, 'tidy -quiet -asxhtml -utf8 --show-body-only yes -
+-show-warnings no --tidy-mark no --write-back yes');" -- This is the fastest fix, but not very elegant, since it doesn't solve the general problem.
+
+2) Make it configurable via ikiwiki.setup as e.g.with the tags plugin. Haven't looked into this code yet.
--- /dev/null
+[[plugins/lockedit]] adds the form fields for a [[pagespec]] to preferences. This pagespec should be supplied "raw"; i.e., without quotes around it. Inexperienced users (such as [[myself|jondowland]]) may provide an invalid pagespec, such as one with quotes on it. This will be merrily accepted by the form, but will cause no locking to take place.
+
+Perhaps some validation should be performed on the pagespec and the form-submission return include "warning: this pagespec is invalid" or "warning: this pagespec does not match any existing pages" or similar.
--- /dev/null
+As mentioned on IRC, I think a cheap form of [[todo/ACL]] can be maintained using [OpenID in ikiwiki](http://packages.qa.debian.org/libn/libnet-openid-consumer-perl.html).
+
+Say I want to limit edits to [wiki.webvm.net](http://wiki.webvm.net/) to users of that machine. For the user 'hendry' I create a http://hendry.webvm.net/ OpenID (which actually delegates to http://hendry.myopenid.com/). And likewise for other users.
+
+So I suggest an ikiwiki configuration like:
+
+ users => ["*.webvm.net"],
+
+Would only allow edits from openIDs of that form.
> ikiwiki on some files that are just large, and cannot reproduce any
> problems, so it must be something in the specific file. (A perl bug is
> also clearly involved here.) --[[Joey]]
+
+The tarball is at http://scratch.madduck.net/__tmp__recentchanges-segfault.tgz - unpack it in `/tmp` and `chdir()` to /tmp/cdt.taF18912, then run
+
+ ikiwiki --setup ikiwiki.setup
+ # segfaults
+ git checkout HEAD^
+ ikiwiki --setup ikiwiki.setup
+ # segfaults
+ rm -rf wc/recentchanges
+ ikiwiki --setup ikiwiki.setup
+ # works
> If you want to gate ikiwiki's various rss feeds to email, that's
> [trivial](http://rss2email.infogami.com/) --[[Joey]]
+
+Also see [[this_wishlist_request|todo/provide_a_mailing_list]]. Sure, you can
+collaborate with RSS and a wiki, but the ikiwiki community is not only made up
+of developers.
OpenID, and see how OpenID works for you. And let me know your feelings about
making such a switch. --[[Joey]]
-[[poll 44 "Accept only OpenID for logins" 17 "Accept only password logins" 32 "Accept both"]]
+[[poll 45 "Accept only OpenID for logins" 17 "Accept only password logins" 33 "Accept both"]]
Quick poll: Do you feel that ikiwiki is fast enough on this server, or
should I move it to my much beefier auxiliary server?
-[[poll 41 "It's fast enough" 5 "It's too slow!" 4 "No opinion"]]
+[[poll 40 "It's fast enough" 6 "It's too slow!" 4 "No opinion"]]
If you have specifics on performance issues, you might mention them on the
[[discussion]] page.
--- /dev/null
+[[template id=plugin name=hnb author="[[XTaran]]"]]
+[[tag type/format]]
+
+This plugin allows ikiwiki to process `.hnb` XML files, as created by
+the Hierachical Notebook [hnb](http://hnb.sourceforge.net/). To use it, you need to have
+hnb installed, since it uses the commandline interface of `hnb` program.
+
+It is roughly based on the `otl` plugin but uses `mktemp` to create temporary files since `hnb` has no "quiet" switch and otherwise the hnb version number and other as well as the output file name always would be in the output itself.
+
+For now it's available for download at [http://noone.org/hnb/hnb.pm](http://noone.org/hnb/hnb.pm)
+
+TODO: Make a switch to allow both HTML export routines of hnb (`export_html` and `export_htmlcss`) to be used.
--- /dev/null
+[[!template id=plugin name=tex4ht core=0 author="[[DavidBremner]]"]]
+
+I have written a simple wrapper around tex4ht to convert tex files to html. This is slow, and currently noisy. I do not recommend it for running from cgi. But for interactive conversion of
+my old tex4ht based home page, it seems to work OK.
+
+The current version is available from
+[git](http://pivot.cs.unb.ca/git?p=ikiperl.git;a=blob_plain;f=IkiWiki/Plugin/tex4ht.pm;hb=HEAD)
+
+[[!tag type/slow]]
--David Riebenbauer <davrieb@htu.tugraz.at>
--- AOLMODE=true echo "I too would really like this feature, which would make cgi free life much
+AOLMODE=true echo "I too would really like this feature, which would make cgi free life much
better" --[[DavidBremner]]
+
+Please make the actual text used a template some way or another. I may want `map` instead of `inline`. --[[madduck]]
--- /dev/null
+
+A minor nitpick: if, while editing, you preview your page two times without changing anything, the second time produces an error. --[[buo]]
-I'm going to look at merging this with potwiki.vim (a vim-based personal wiki) so that you can follow wiki-links and auto-create pages etc., direct from vim. (I'm writing this incase I don't get around to it) -- [[users/JonDowland]]
+I'm going to look at merging this with potwiki.vim (a vim-based personal wiki) so that you can follow wiki-links and auto-create pages etc., direct from vim. (I'm writing this incase I don't get around to it) -- [[JonDowland]]
> footer, or is added with a taglink directive. Think that's good enough?
> --[[Joey]]
+>> yes, that would be better! --[[madduck]]
+
See also: [[bugs/tags_base_dir_not_used_when_creating_new_tags]]
[[tag wishlist]]
--- /dev/null
+I am aware that you (Joey) [[made_a_choice_against_a_mailing_list|contact]],
+but I would like to see you reconsider.
+
+The wiki works well for bugs and
+collaborating on the software, but not for simple user support issues. For
+instance, I spent the last three days waiting for any form of reply to my
+question on IRC (none so far):
+
+ 09 15:49 < madduck> any ideas how to implement a two-level menu
+ 09 15:40 < madduck> like http://www.abacons.ch/leistungen/treuhand.html ?
+ 09 15:50 < madduck> the top bar are the main sections
+ 09 15:50 < madduck> and then i might need subsections (further down) under each
+ 09 15:50 < madduck> i'd like to do this without hardcoding sections in the template
+ 09 15:50 < madduck> but at least the main sections are to appear on all pages
+ 09 15:50 < madduck> so the template needs a slot, i just wonder how best to fill it
+ 09 15:51 < madduck> i can only ever use one navbar it seems
+ 09 15:51 < madduck> and i already need the sidebar for something else
+
+I would not know where to take this question on the wiki itself.
+
+A mailing list is made for these kind of questions, and as we pick up even
+more users, the number of such requests will also increase. --[[madduck]]
+
+> I wouldn't mind a mailing list myself. For many people, e-mail is more
+> efficient to process, particularly offline, than wiki pages. Also,
+> ikiwiki's discussion pages require a fair amount of discipline from
+> users to make it easy to follow a long discussion. On the other hand,
+> it would be interesting to make improvements to ikiwiki
+> (read: plugins) to to see if it's possible to accomodate both
+> mail people and online people.
+> --[liw](http://liw.fi)
+
+>> The [Zwiki](http://zwiki.org) project has ideas to mine in this area. We explored various permutations of wiki and mail list.
+>> Currently Zwiki's [email features](http://zwiki.org/Mail) are good enough that we use it as the mail list and don't run separate
+>> ml software. This is simple and mostly satisfying. Now and then we miss the familiarity and industrial
+>> strength of a standard mail list and its simple time-based archive. We do gateway with [gmane](http://news.gmane.org/gmane.comp.web.zope.zwiki) so people
+>> can use that as an alternative. I'm happy to chat about this, ping me..
+>> --[sm](http://joyful.com)
+
+[[tag wishlist]]
--- /dev/null
+It would rock if I could view diffs from the web without going via feeds. I envision toggle-style buttons on the recentchanges page, or just links to the CGI, which then displays the diff... --[[madduck]]
+
+[[tag wishlist]]
A new ikiwiki user, looking at ikiwiki both for his personal site but also as a team-documentation management system for a small-sized group of UNIX sysadmins.
-(currently non-ikiwiki) Homepage: http://alcopop.org/
+* (currently non-ikiwiki) Homepage: <http://alcopop.org/>
+* potential future (ikiwiki) Homepage: <http://jmtd.net/>
-<http://people.debian.org/~madduck>
\ No newline at end of file
+<http://people.debian.org/~madduck>
+
+I track this site with the following feed:
+
+[[inline pages="internal(recentchanges/change_*) and !author(http://madduck.net/)"
+feedonly=yes atom=no]]
--- /dev/null
+[Homepage](http://noone.org/abe/), [Blog](http://noone.org/blog)
+
+Currently only use it to play around (so no link to any ikiwiki yet), but I really like it and [I see it as a potential WML killer](http://noone.org/blog/English/Computer/Web/WML/Is%20ikiwiki%20a%20WML%20killer%3f.futile). It also reminds me to Blosxom somehow although I think it won't be a Blosxom killer. OTOH I know of people who moved from Blosxom to Ikiwiki as blogging engine. :)
+
+Probably will use it for some parts of my website revamp and for wikiizing my [[/plugins/contrib/hnb]] note files.