1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
|
Seems like there should be a page for you to post your thoughts about
ikiwiki, both pro and con, anything that didn't work, ideas, or whatever.
Do so here..
Note that for more formal bug reports or todo items, you can also edit the
[[bugs]] and [[todo]] pages.
# Installation/Setup questions
I have just installed ikiwiki and it works - at least I have the example index.mdwn page
compiled and visible. However I have a few issues/problems:-
* A couple of the 'optional' Perl modules aren't optional, you can't install ikiwiki without them,
these are HTML::Template and HTML::Scrubber (at least I think it was these two, it's a bit messy
to go back and find out).
> You're right, HTML::Template is required. HTML::Scrubber is only required
> in the default configuration, and is optional if the htmlscrubber plugin
> is disabled. --[[Joey]]
* I don't seem to have got an ikiwiki man page created.
> It should be installed in /usr/share/man, or a similar directory
> depending on how your perl is set up and how you did the install.
> --[[Joey]]
> 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
> 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
> more sensible. [[Chris]]
* Running "ikiwiki --setup ikiwiki.setup" doesn't do anything. I have edited ikiwiki.setup to
my local settings. There are no errors but neither does anything get compiled. An ikiwiki
command to explicitly do the compile works fine. Am I misunderstanding something here?
> Further tests indicate that ikiwiki isn't seeing changed files so doesn't always rebuild.
> 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
either though it was the command line I originally used to compile. After a long interval I 'touch'ed
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!
> ikiwiki only compiles files whose modification times have changed. It
> should see any change made as close as a second after the last compile.
> When run with --setup, ikiwiki always rebuilds every file in the wiki. If
> --setup is not working, you must have it pointed at the wrong path or
> something; you can pass -v to see what it's doing. I don't know why it
> would not see recently changed files; you could try stracing it.
> --[[Joey]]
> OK, thanks, I don't quite know what was happening before but it seems to be working right now.
> --[[Chris]]
>> Weird. I wish I knew what happened, but as it's working now, I'm
>> guessing some kind of user error was involved. --[[Joey]]
* I wish there was a mailing list, much easier for this sort of stuff than this, apart from
anything else I get to use a decent editor.
----
# Excellent - how do I translate a TWiki site?
I just discovered ikiwiki quite by chance, I was looking for a console/terminal
menu system and found pdmenu. So pdmenu brought me to here and I've found ikiwiki!
It looks as if it's just what I've been wanting for a long time. I wanted something
to create mostly text web pages which, as far as possible, have source which is human
readable or at least in a standard format. ikiwiki does this twice over by using
markdown for the source and producing static HTML from it.
I'm currently using TWiki and have a fair number of pages in that format, does
anyone have any bright ideas for translating? I can knock up awk scripts fairly
easily, perl is possible (but I'm not strong in perl).
> Let us know if you come up with something to transition from the other
> format. Another option would be writing a ikiwiki plugin to support the
> TWiki format. --[[Joey]]
> 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).
>
> 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.
>
> We will post the scripts as soon as we have them complete enough to convert our wikis.
>
> -- Josh Triplett
>> Thanks for an excellent Xmas present, I will appreciate the additional
>> users this will help switch to ikiwiki! --[[Joey]]
----
# OpenID
I just figured I'd edit something on the page with my OpenID, since you've implemented it! --*[Kyle](http://kitenet.net/~kyle/)*=
> Kyle, If you like openid, I can switch your personal wiki over to use your openid. --[[Joey]]
----
# ACL
> Moved to [[todo/ACL]] --[[Joey]]
----
Some questions about the RecentChanges function. -- Ethan
> (Moved to [[todo/recentchanges]] --[[Joey]])
----
Also, I'd like to request another template parameter which is just
$config{url}. That way you won't have to hard-code the URL of the wiki into
the template. -- Ethan
> That's already available in the BASEURL parameter. --[[Joey]]
----
# Canonical feed location?
Moved to [[todo/canonical_feed_location]] --[[Joey]]
----
# asciidoc or txt2tags ?
Any plugins or support for using asciidoc or txt2tags as the wiki language and/or exporting to asciidoc or txt2tags?
> No, but it should be quite easy to write such a plugin. The otl plugin
> is a good example of writing a formatting plugin that uses an external
> conversion program, like asciidoc or txt2tags. --[[Joey]]
----
# LaTeX support?
Any plugins or support for exporting to LaTeX?
(If not could use asciidoc or txt2tags mentioned above to generated LaTeX.)
> It's already [[been_requested|todo/latex]], although perhaps not
> working the way you're thinking of. Noone is currently working on it.
> --[[Joey]]
>> I did some tests with using Markdown and a customized HTML::Latex and html2latex
>> and it appears it will work for me now. (I hope to use ikiwiki for many
>> to collaborate on a printed book that will be generated at least once per day in PDF format.)
>>
>> --JeremyReed
----
# Using with CVS?
Any examples of using ikiwiki with cvs?
> No, although the existing svn backend could fairly esily be modified into
> a CVS backend, by someone who doesn't mind working with CVS. --[[Joey]]
----
# Show differences before saving page?
It would be nice to be able to have a button to show "Differences" (or "Show Diff") when
editing a page. Is that an option that can be enabled?
> It's doable, it could even be done by a [[todo/plugin]], I think.
> --[[Joey]]
----
# Max submit size?
Any setting for limiting how many kilobytes can be submitted via the "edit" form?
-- [[JeremyReed]]
> Not currently. Worried about abuse? --[[Joey]]
>> 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.
>> I read that textarea max bytes may be 500 lines or 28000 characters or 30000 characters or 64kB. It seems like it
>> varies and I didn't test myself, because I guess it may depend on different clients and different HTTP servers.
>> This could be checked using javascript on the client side (before submitting) and by checking size on server side (before saving). --[[JeremyReed]]
>>> The absolute limit varies by browser. If there are web servers that
>>> also limit it, I don't know of them. --[[Joey]]
----
# Disable sub-discussion pages?
Moved to [[bugs]] -- [[Joey]]
----
# wiki\_file\_regexp and RCS ,v files
I have RCS ,v files in my source directory. But get many "skipping bad filename" warnings.
Also I don't see wiki\_file\_regexp documented. Because it is used with $config{wiki\_file\_regexp} I assume it can be set in the ikiwiki.setup.
I added a comma to it in my IkiWiki.pm in the defaultconfig(). But that was wrong (so I reverted back), because then the ,v files were copied to my www tree.
What is the correct way to include ,v RCS revision files in my source tree without receiving the "bad" messages and without copying over to www tree?
-- [[JeremyReed]]
> Add the ,v to the $config{wiki_file_prune_regexps} array. This is how we
> skip equivilant files from other revision control systems too.
> --[[Joey]]]
----
# Textile Plugin
It was trivial, but I put together a plugin that uses the Textile markup
language, which I find to be the most superior of the various options for
that sort of thing. Where or how do I submit it for inclusion?
> You can post it to [[plugins/contrib]]. --[[Joey]]
|