----
-# 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?
>>
>> --JeremyReed
+>>> Have a look at [pandoc](http://code.google.com/p/pandoc/). It can make PDFs via pdflatex. --[[roktas]]
+
----
# Using with CVS?
----
-# 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
> Maybe, although it would need to take the critisism at
> http://www.cs.tut.fi/~jkorpela/forms/accesskey.html into account.
+>> Thank you for that link. Given that the edit link is the first thing you tab to
+>> in the current layout, I guess it isn't all that necessary. I have had a
+>> a user complaint recently that Alt-e in oddmuse was overriding his access
+>> to the browser menu.
+
----
# Editing the style sheet.
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.
Ok, that's my last 2 cents for a while. --[Mazirian](http://mazirian.com)
+> I don't support editing it, but if/when ikiwiki gets file upload support,
+> it'll be possible to upload a style sheet. (If .css is in the allowed
+> extensions list.. no idea how safe that would be, a style sheet is
+> probably a great place to put XSS attacks and evil javascript that would
+> be filtered out of any regular page in ikiwiki). --[[Joey]]
+
+>> I hadn't thought of that at all. It's a common feature and one I've
+>> relied on safely, because the wikis I am maintaining at the moment
+>> are all private and restricted to trusted users. Given that the whole
+>> point of ikiwiki is to be able to access and edit via the shell as
+>> well as the web, I suppose the features doesn't add a lot. By the
+>> way, the w3m mode is brilliant. I haven't tried it yet, but the idea
+>> is great.
+
----
-# Disable build/install requirement on PerlMagick
+# 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
+
+>>> Well, it's a simple [[patch|patchqueue/full_paths_in_recentchanges]].
+>>> For a limited time I have that patch running on this wiki. Undecided if
+>>> I like it or not; the width is not really a problem due to the design
+>>> of the recentchanges page, but all those paths do clutter up the page
+>>> somewhat. Comments? --[[Joey]]
+
+----
+
+# Should not create an existing page
+
+This might be a bug, but will discuss it here first.
+Clicking on an old "?" or going to a create link but new Markdown content exists, should not go into "create" mode, but should do a regular "edit".
+
+> I belive that currently it does a redirect to the new static web page.
+> At least that's the intent of the code. --[[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
+
+What do you think about refreshing RecentChanges page (via Meta Refresh Tag)?
+It can be useful for users like me which rather prefer watching the last changes
+in WWW browser tab than subscribing to page. --Pawel
+
+> Depends, if it were done the time period should be made configurable.
+> Unwanted server load due to refeshing could be a problem for some.
+> --[[Joey]]
+
+>> 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
-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]]
+>>> Seems reasonable --[[Joey]]