# ACL
-How about adding ACL? So that you can control which users are allowed
-to read, write certain pages. The moinmoin wiki has that, and it is
-something, that I think is very valuable.
-
-> ikiwiki currently has only the most rudimentary access controls: pages
-> can be locked, or unlocked and only the admin can edit locked pages. That
-> could certianly be expanded on, although it's not an area that I have an
-> overwhelming desire to work on myself right now. Patches appreciated and
-> I'll be happy to point you in the right directions.. --[[Joey]]
-
->> I'm really curious how you'd suggest implementing ACLs on reading a page.
->> It seems to me the only way you could do it is .htaccess DenyAll or something,
->> and then route all page views through ikiwiki.cgi. Am I missing something?
->> --[[Ethan]]
-
->>> Or you could just use apache or whatever and set up the access controls
->>> there. Of course, that wouldn't integrate very well with the wiki,
->>> unless perhaps you decided to use http basic authentication and the
->>> httpauth plugin for ikiwiki that integrates with that.. --[[Joey]]
-
->>>> Which would rule out openid, or other fun forms of auth. And routing all access
->>>> through the CGI sort of defeats the purpose of ikiwiki. --[[Ethan]]
+> Moved to [[todo/ACL]] --[[Joey]]
----
# Canonical feed location?
-Any way to use `inline` but point the feed links to a different feed on the
-same site? I have news in news/*, a news archive in news.mdwn, and the
-first few news items on index.mdwn, but I don't really want two separate
-feeds, one with all news and one with the latest few articles; I'd rather
-point the RSS feed links of both to the same feed. (Which one, the one
-with all news or the one with the latest news only, I don't know yet.)
-
-> Not currently. It could be implemented, or you could just turn off the
-> rss feed for the index page, and manually put in a wikilink to the news
-> page and rss feed. --[[Joey]]
-
->> That wouldn't use the same style for the RSS and Atom links, and it
->> wouldn't embed the feed link into `<head>` so that browsers can automatically
->> find it.
+Moved to [[todo/canonical_feed_location]] --[[Joey]]
----
----
-# Using with RCS?
-
-Any examples of using co(1), ci(1) and other RCS related tools with ikiwiki?
-
-> I don't belive that RCS offers enough SCM features to be useable as a
-> fullfledged backend to ikiwiki. For one thing, there's no way to have
-> hook scripts run when changes are ci'd, is there? So you'd have to ci and
-> then manually run ikiwiki. It should be possible to do an RCS backend
-> that supports web commits with ci, and history (parsing the rcs files by
-> hand?). If you're a masochist. :-) --[[Joey]]
-
->> It does have history using rlog(1) which is similar format to "cvs log".
->> I don't think it has any possible hooks. What would happen if I call
->> ikiwiki directly from rcs_commit? (I didn't try yet.) On that note,
->> I don't see any way for ikiwiki to generate a single file, but I guess
->> that doesn't matter as --refresh should be fast enough.
->> I made a Rcs/rcs.pm plugin from Stub. I have been testing it some.
->>
->> --JeremyReed
-
->> I made a working rcs plugin. And I made a RCS-to-web CGI. Details
->> at [[patchqueue/rcs_(third-party_plugin)]]
->> --[[JeremyReed]]
->>
->> (Moved to patchqueue --[[Joey]])
-
-----
-
# Using with CVS?
Any examples of using ikiwiki with cvs?
Any setting for limiting how many kilobytes can be submitted via the "edit" form?
-- [[JeremyReed]]
-> Not currently. Worried about abuse? -man -[[Joey]]
+> 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?
-Any setting to disable having a discussion of a discussion?
-The [[features]] page says every page, but I don't want every page.
-I do want discussion subpage, but I don't want to have, for example: discussion/ discussion/ discussion.
--- [[JeremyReed]]
+Moved to [[bugs]] -- [[Joey]]
----
-# wiki\_file\_regexp and RCS ,v files
+# 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?
-I have RCS ,v files in my source directory. But get many "skipping bad filename" warnings.
+> You can post it to [[plugins/contrib]]. --[[Joey]]
-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.
+>> Thanks. I tried using the "Add new post" form there, but apparently made a [mess of things somehow](http://ikiwiki.kitenet.net/contrib/textile___40__third-party_plugin__41__.html). Sorry about that.
-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?
+>>> No problem, the contrib form had the wrong rootpage setting. I've fixed
+>>> it up and moved it to the right place. A copyright statement would be
+>>> nice.
--- [[JeremyReed]]
+> How does one go about making a markup language added by means of a plugin, the default markup language. In other words, I would like the index page to be written in Textile.
+> If I include a index.txtl (where txtl is the extension I have assigned to be handled by the textile plugin), ikiwiki will ignore it and make a new index.mdwn.
-----
+>> Sounds like a bug; it should be configurable via `default_pageext`, but
+>> I suspect that currently if there are two competing files with different
+>> extensions that make the same page, they fight it out and some random
+>> one "wins"
+>>
+>> Until I fix that, you can avoid the one from the underlay directory by
+>> setting `underlaydir` to point to an empty directory. --[[Joey]]
+>>
+>> Ok, fixed (in svn), it will now prefer files in the srcdir over files
+>> in the underlaydir that build the same page, no matter what extension.
-# Textile Plugin
+>>> Thanks, Joey, much appreciated. --[Mazirian](http://mazirian.com)
+
+# Access Keys
-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?
\ No newline at end of file
+Would anyone else find this a valuable addition. In oddmuse and instiki (the only other
+wiki engines I am currently using, the edit, home, and submit link tags have an
+accesskey attribute. I find it nice not to have to resort to the mouse for those
+actions. However, it may not be something everyone appreciates. Any thoughts?
+--[Mazirian](http://mazirian.com)
\ No newline at end of file