X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/b5e2afa94390dd3349fed81f72892da3beba56ed..5f785c8503e6a25854c10612d28fb86a9387b12f:/doc/index/discussion.mdwn?ds=sidebyside diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn index 741a8d9dc..d409a30e2 100644 --- a/doc/index/discussion.mdwn +++ b/doc/index/discussion.mdwn @@ -144,6 +144,8 @@ Any plugins or support for exporting to LaTeX? >> >> --JeremyReed +>>> Have a look at [pandoc](http://code.google.com/p/pandoc/). It can make PDFs via pdflatex. --[[roktas]] + ---- # Using with CVS? @@ -199,6 +201,11 @@ actions. However, it may not be something everyone appreciates. Any thoughts? > 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. @@ -206,6 +213,20 @@ actions. However, it may not be something everyone appreciates. Any thoughts? 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 @@ -215,3 +236,78 @@ in the Makefile. But still failed. My workaround was to remove "img" from the bu 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 + +---- + +# 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]] + +---- + +# 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]] + +---- + +# Fall back for templatedir + +It would be nice if you didn't have to copy all templates to your custom _templatedir_ +so you only have your customizations there. +And then have it fall back to the location as configured at build time (like /usr/share/ikiwiki/templates/). +This would be similar to _underlaydir_. I don't think any extra configuration directive is needed. +As it is now, RecentChanges will have Perl CGI error and Preferences will be an empty page, if you don't have corresponding templates. +I can quickly make a patch and submit to the patch queue. Any comments? + +> I'd probably accept a patch immediately. --[[Joey]]