1 Seems like there should be a page for you to post your thoughts about
2 ikiwiki, both pro and con, anything that didn't work, ideas, or whatever.
5 Note that for more formal bug reports or todo items, you can also edit the
6 [[bugs]] and [[todo]] pages.
8 # Installation/Setup questions
10 I have just installed ikiwiki and it works - at least I have the example index.mdwn page
11 compiled and visible. However I have a few issues/problems:-
13 * A couple of the 'optional' Perl modules aren't optional, you can't install ikiwiki without them,
14 these are HTML::Template and HTML::Scrubber (at least I think it was these two, it's a bit messy
15 to go back and find out).
17 > You're right, HTML::Template is required. HTML::Scrubber is only required
18 > in the default configuration, and is optional if the htmlscrubber plugin
19 > is disabled. --[[Joey]]
21 * I don't seem to have got an ikiwiki man page created.
23 > It should be installed in /usr/share/man, or a similar directory
24 > depending on how your perl is set up and how you did the install.
27 > Found it, in /usr/local/share/man, since no other man pages are in either /usr/share/man or in /usr/local/share/man the ikiwiki
28 > man page is a bit lonely, and more to the point not on my MANPATH. Still I have found it now, I'll just move it to somewhere
29 > more sensible. [[Chris]]
31 * Running "ikiwiki --setup ikiwiki.setup" doesn't do anything. I have edited ikiwiki.setup to
32 my local settings. There are no errors but neither does anything get compiled. An ikiwiki
33 command to explicitly do the compile works fine. Am I misunderstanding something here?
35 > Further tests indicate that ikiwiki isn't seeing changed files so doesn't always rebuild.
36 > How does ikiwiki decide when to rebuild? I tried a full command line like "ikiwiki --verbose ikiwiki ~/public_html/ikiwiki --url=http://www.isbd.ltd.uk/~chris/ikiwiki/" and that doesn't do anything
37 either though it was the command line I originally used to compile. After a long interval I 'touch'ed
38 the files and then it *did* compile but 'touch'ing the files after a few minutes only doesn't seem to force a recompile. I'm even more confused!
40 > ikiwiki only compiles files whose modification times have changed. It
41 > should see any change made as close as a second after the last compile.
42 > When run with --setup, ikiwiki always rebuilds every file in the wiki. If
43 > --setup is not working, you must have it pointed at the wrong path or
44 > something; you can pass -v to see what it's doing. I don't know why it
45 > would not see recently changed files; you could try stracing it.
48 > OK, thanks, I don't quite know what was happening before but it seems to be working right now.
51 >> Weird. I wish I knew what happened, but as it's working now, I'm
52 >> guessing some kind of user error was involved. --[[Joey]]
54 * I wish there was a mailing list, much easier for this sort of stuff than this, apart from
55 anything else I get to use a decent editor.
58 # Excellent - how do I translate a TWiki site?
60 I just discovered ikiwiki quite by chance, I was looking for a console/terminal
61 menu system and found pdmenu. So pdmenu brought me to here and I've found ikiwiki!
62 It looks as if it's just what I've been wanting for a long time. I wanted something
63 to create mostly text web pages which, as far as possible, have source which is human
64 readable or at least in a standard format. ikiwiki does this twice over by using
65 markdown for the source and producing static HTML from it.
67 I'm currently using TWiki and have a fair number of pages in that format, does
68 anyone have any bright ideas for translating? I can knock up awk scripts fairly
69 easily, perl is possible (but I'm not strong in perl).
71 > Let us know if you come up with something to transition from the other
72 > format. Another option would be writing a ikiwiki plugin to support the
73 > TWiki format. --[[Joey]]
75 > Jamey Sharp and I have a set of scripts in progress to convert other wikis to ikiwiki, including history, so that we can migrate a few of our wikis. We already have support for migrating MoinMoin wikis to ikiwiki, including conversion of the entire history to Git. We used this to convert the [XCB wiki](http://xcb.freedesktop.org/wiki/) to ikiwiki; until we finalize the conversion and put the new wiki in place of the old one, you can browse the converted result at <http://xcb.freedesktop.org/ikiwiki>. We already plan to add support for TWiki (including history, since you can just run parsecvs on the TWiki RCS files to get Git), so that we can convert the [Portland State Aerospace Society wiki](http://psas.pdx.edu) (currently in Moin, but with much of its history in TWiki, and with many of its pages still in TWiki format using Jamey's TWiki format for MoinMoin).
77 > Our scripts convert by way of HTML, using portions of the source wiki's code to render as HTML (with some additional code to do things like translate MoinMoin's `\[[TableOfContents]]` to ikiwiki's `\[[toc ]]`), and then using a modified [[cpan HTML::WikiConverter]] to turn this into markdown and ikiwiki. This produces quite satisfactory results, apart from things that don't have any markdown equivalent and thus remain HTML, such as tables and definition lists. Conversion of the history occurs by first using another script we wrote to translate MoinMoin history to Git, then using our git-map script to map a transformation over the Git history.
79 > We will post the scripts as soon as we have them complete enough to convert our wikis.
83 >> Thanks for an excellent Xmas present, I will appreciate the additional
84 >> users this will help switch to ikiwiki! --[[Joey]]
90 I just figured I'd edit something on the page with my OpenID, since you've implemented it! --*[Kyle](http://kitenet.net/~kyle/)*=
92 > Kyle, If you like openid, I can switch your personal wiki over to use your openid. --[[Joey]]
98 > Moved to [[todo/ACL]] --[[Joey]]
102 Some questions about the RecentChanges function. -- Ethan
104 > (Moved to [[todo/recentchanges]] --[[Joey]])
108 Also, I'd like to request another template parameter which is just
109 $config{url}. That way you won't have to hard-code the URL of the wiki into
110 the template. -- Ethan
112 > That's already available in the BASEURL parameter. --[[Joey]]
116 # Canonical feed location?
118 Moved to [[todo/canonical_feed_location]] --[[Joey]]
122 # asciidoc or txt2tags ?
124 Any plugins or support for using asciidoc or txt2tags as the wiki language and/or exporting to asciidoc or txt2tags?
126 > No, but it should be quite easy to write such a plugin. The otl plugin
127 > is a good example of writing a formatting plugin that uses an external
128 > conversion program, like asciidoc or txt2tags. --[[Joey]]
134 Any plugins or support for exporting to LaTeX?
135 (If not could use asciidoc or txt2tags mentioned above to generated LaTeX.)
137 > It's already [[been_requested|todo/latex]], although perhaps not
138 > working the way you're thinking of. Noone is currently working on it.
141 >> I did some tests with using Markdown and a customized HTML::Latex and html2latex
142 >> and it appears it will work for me now. (I hope to use ikiwiki for many
143 >> to collaborate on a printed book that will be generated at least once per day in PDF format.)
151 Any examples of using ikiwiki with cvs?
153 > No, although the existing svn backend could fairly esily be modified into
154 > a CVS backend, by someone who doesn't mind working with CVS. --[[Joey]]
158 # Show differences before saving page?
160 It would be nice to be able to have a button to show "Differences" (or "Show Diff") when
161 editing a page. Is that an option that can be enabled?
163 > It's doable, it could even be done by a [[todo/plugin]], I think.
170 Any setting for limiting how many kilobytes can be submitted via the "edit" form?
173 > Not currently. Worried about abuse? --[[Joey]]
175 >> I didn't want it abused accidently or with malice. I was thinking that Perl's CGI.pm would handle this, but I don't see that.
176 >> I read that textarea max bytes may be 500 lines or 28000 characters or 30000 characters or 64kB. It seems like it
177 >> varies and I didn't test myself, because I guess it may depend on different clients and different HTTP servers.
178 >> This could be checked using javascript on the client side (before submitting) and by checking size on server side (before saving). --[[JeremyReed]]
180 >>> The absolute limit varies by browser. If there are web servers that
181 >>> also limit it, I don't know of them. --[[Joey]]
185 # Disable sub-discussion pages?
187 Moved to [[bugs]] -- [[Joey]]
193 Would anyone else find this a valuable addition. In oddmuse and instiki (the only other
194 wiki engines I am currently using, the edit, home, and submit link tags have an
195 accesskey attribute. I find it nice not to have to resort to the mouse for those
196 actions. However, it may not be something everyone appreciates. Any thoughts?
197 --[Mazirian](http://mazirian.com)
199 > Maybe, although it would need to take the critisism at
200 > http://www.cs.tut.fi/~jkorpela/forms/accesskey.html into account.
202 >> Thank you for that link. Given that the edit link is the first thing you tab to
203 >> in the current layout, I guess it isn't all that necessary. I have had a
204 >> a user complaint recently that Alt-e in oddmuse was overriding his access
205 >> to the browser menu.
209 # Editing the style sheet.
211 It would be nice to be able to edit the stylesheet by means of the cgi. Or is this possible? I wasn't able to achieve it.
212 Ok, that's my last 2 cents for a while. --[Mazirian](http://mazirian.com)
214 > I don't support editing it, but if/when ikiwiki gets file upload support,
215 > it'll be possible to upload a style sheet. (If .css is in the allowed
216 > extensions list.. no idea how safe that would be, a style sheet is
217 > probably a great place to put XSS attacks and evil javascript that would
218 > be filtered out of any regular page in ikiwiki). --[[Joey]]
220 >> I hadn't thought of that at all. It's a common feature and one I've
221 >> relied on safely, because the wikis I am maintaining at the moment
222 >> are all private and restricted to trusted users. Given that the whole
223 >> point of ikiwiki is to be able to access and edit via the shell as
224 >> well as the web, I suppose the features doesn't add a lot. By the
225 >> way, the w3m mode is brilliant. I haven't tried it yet, but the idea
230 # Disable build/install requirement on PerlMagick
232 Some installs of PerlMagick require X11. I tried to first disable using "img" by using "--disable-plugin img"
233 in the Makefile. But still failed. My workaround was to remove "img" from the bundle in IkiWiki/Plugin/goodstuff.pm
234 before building. What is the recommended way to install ikiwiki without "img" support? --[[JeremyReed]]
236 > I've fixed this in svn so plugins in goodstuff can be disabled. --[[Joey]]