X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/ba53b64fb040310cfe8fc22f668ee5c744355a92..d05d052bff599327cf43b6f00e337197f1d2ab18:/doc/index/discussion.mdwn diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn index ff2eb98eb..3c51ad99e 100644 --- a/doc/index/discussion.mdwn +++ b/doc/index/discussion.mdwn @@ -95,28 +95,7 @@ I just figured I'd edit something on the page with my OpenID, since you've imple # 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]] ---- @@ -136,20 +115,7 @@ the template. -- Ethan # 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 `` so that browsers can automatically ->> find it. +Moved to [[todo/canonical_feed_location]] --[[Joey]] ---- @@ -180,28 +146,6 @@ Any plugins or support for exporting to LaTeX? ---- -# 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 - ----- - # Using with CVS? Any examples of using ikiwiki with cvs? @@ -218,3 +162,54 @@ 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]] + +---- + +# Access Keys + +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) + +> Maybe, although it would need to take the critisism at +> http://www.cs.tut.fi/~jkorpela/forms/accesskey.html into account. + +---- + +# 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) + +---- + +# 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]]