X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/875f69ad8ad953e7de1b4c7d388f5c0258615711..37b5b0541f0446d792aa8607f273cea41ea04303:/doc/index/discussion.mdwn?ds=sidebyside diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn index 5b6a659c7..6b233882e 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]] ---- @@ -172,18 +138,11 @@ Any plugins or support for exporting to LaTeX? > working the way you're thinking of. Noone is currently working on it. > --[[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]] +>> 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 ---- @@ -203,3 +162,115 @@ 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. + +>> 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 + +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 \ No newline at end of file