X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/9758a2e8da581bf19441cdf26ecd34e607ce80cd..42140a88fd366437faa25f8206f995c3a88e3662:/doc/index/discussion.mdwn diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn index d670796d4..25723ec55 100644 --- a/doc/index/discussion.mdwn +++ b/doc/index/discussion.mdwn @@ -85,74 +85,6 @@ easily, perl is possible (but I'm not strong in perl). ---- -# 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 - -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]] - ----- - -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? - -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. - ----- - # asciidoc or txt2tags ? Any plugins or support for using asciidoc or txt2tags as the wiki language and/or exporting to asciidoc or txt2tags? @@ -178,33 +110,7 @@ Any plugins or support for exporting to LaTeX? >> >> --JeremyReed ----- - -# 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]]) +>>> Have a look at [pandoc](http://code.google.com/p/pandoc/). It can make PDFs via pdflatex. --[[roktas]] ---- @@ -232,37 +138,135 @@ editing a page. Is that an option that can be enabled? 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? +# Access Keys -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]] +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. ---- -# wiki\_file\_regexp and RCS ,v files +# Editing the style sheet. -I have RCS ,v files in my source directory. But get many "skipping bad filename" warnings. +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) -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. +> 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]] -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? +>> 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. --- [[JeremyReed]] +---- + +# 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.) ---- -# Textile Plugin +# 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 -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 +>>> Seems reasonable --[[Joey]]