Note that for more formal bug reports or todo items, you can also edit the
[[bugs]] and [[todo]] pages.
+[[toc ]]
+
# Installation/Setup questions
I have just installed ikiwiki and it works - at least I have the example index.mdwn page
----
-# 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?
----
-# Disable sub-discussion pages?
-
-Moved to [[bugs]] -- [[Joey]]
-
-----
-
# Access Keys
Would anyone else find this a valuable addition. In oddmuse and instiki (the only other
----
-# Disable build/install requirement on PerlMagick
-
-Some installs of PerlMagick require X11. I tried to first disable using "img" by using "--disable-plugin img"
-in the Makefile. But still failed. My workaround was to remove "img" from the bundle in IkiWiki/Plugin/goodstuff.pm
-before building. What is the recommended way to install ikiwiki without "img" support? --[[JeremyReed]]
-
-> I've fixed this in svn so plugins in goodstuff can be disabled. --[[Joey]]
-
-----
-
-# Documentation for banning users?
-
-The [[todo]] page says admins can ban users. Where is this documented? I search the source and found
-set\_banned\_users() which led me to the CGI "preferences" form for the admin. Now logged in as an admin (as defined in my setup configuration),
-I see the field for this. But no details on how to use it. From the source it appears to be a space-delimited list of usernames. (I didn't test yet.)
-
-Can you please provide a [[/banned_users]] documentation about "banning" users function linked from the [[Features]] page and maybe [[security]] page and linked from the "preferences" for the admin?
-(I don't do this myself as I am unsure about this and still reading the code about banning users.)
-
-----
-
-# Documentation for locking pages?
-
-The [[features]] page, the [[todo]] page and the [[usage]] manual page say pages can be locked and only the admin can edit locked pages.
-Where is locking pages documented? ... A moment later, from searching source I found this is configured via the preferences for the admin
-and that links to [[pagespec]].
-
-Can you please provide a [[/page_locking]] doc about locking pages linked from the [[features]] page and elsewhere? And have that link to [[pagespec]]?
-(I don't do this myself as I am unsure about this and still reading the code about locking pages.)
-
-----
-
# RecentChanges should show path to wiki sub-pages?
The RecentChanges only shows the final file name for the recently changes file,
for example "discussion". It would be more useful to see "index/discussion"
or the path to the sub-page. I think this is handled by the htmllink() routine.
->> IMHO it's a good idea and I like it. Often I can see changes in
->> any discussion page, but I don't know without clicking the link
->> what discussion was changed.
-
->> However, I can see one problem here. You can commit via command line
->> changes in many pages. It will be displayed ugly then, because probably
->> a width of the RecentChanges page will be greater then a width of
->> user's browser. I hate these pages. So I propose to display a list of
->> changed pages in a column, not in a row. --Pawel
+> Went ahead and did this, IMHO the display is ok as-is. --[[Joey]]
----
>> Try at your site: `?page=discussion&from=index&do=create`
>> It brings up an empty textarea to start a new webpage -- even though it already exists here. --reed
+>>> Ah, right. Notice that the resulting form allows saving the page as
+>>> discussion, or users/discussion, but not index/discussion, since this
+>>> page already exists. If all the pages existed, it would do the redirect
+>>> thing. --[[Joey]]
+
----
# Refreshing RecentChanges page
> Unwanted server load due to refeshing could be a problem for some.
> --[[Joey]]
-----
-
-# Fall back for templatedir
-
-It would be nice if you didn't have to copy all templates to your custom _templatedir_
-so you only have your customizations there.
-And then have it fall back to the location as configured at build time (like /usr/share/ikiwiki/templates/).
-This would be similar to _underlaydir_. I don't think any extra configuration directive is needed.
-As it is now, RecentChanges will have Perl CGI error and Preferences will be an empty page, if you don't have corresponding templates.
-I can quickly make a patch and submit to the patch queue. Any comments?
+>> Yes, it should be configurable by ikiwiki admin. I believe he's not
+>> stupid and he will not set too short refresh period to kill his server :)
+>> I propose to add `recentchanges_refresh` variable in ikiwiki setup
+>> to setting refresh period. If it's not defined, then ikiwiki doesn't put
+>> refresh meta tag into `recentchanges.tmpl`. Do you like it? ;) --Pawel
-> I'd probably accept a patch immediately. --[[Joey]]
+>>> Seems reasonable --[[Joey]]