X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/42140a88fd366437faa25f8206f995c3a88e3662..5e9dd45f4bd500b22c25efa2e457a0f9f63db439:/doc/index/discussion.mdwn?ds=sidebyside diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn index 25723ec55..f15d91c6d 100644 --- a/doc/index/discussion.mdwn +++ b/doc/index/discussion.mdwn @@ -5,54 +5,12 @@ Do so here.. Note that for more formal bug reports or todo items, you can also edit the [[bugs]] and [[todo]] pages. -# Installation/Setup questions - -I have just installed ikiwiki and it works - at least I have the example index.mdwn page -compiled and visible. However I have a few issues/problems:- - -* A couple of the 'optional' Perl modules aren't optional, you can't install ikiwiki without them, -these are HTML::Template and HTML::Scrubber (at least I think it was these two, it's a bit messy -to go back and find out). - -> You're right, HTML::Template is required. HTML::Scrubber is only required -> in the default configuration, and is optional if the htmlscrubber plugin -> is disabled. --[[Joey]] - -* I don't seem to have got an ikiwiki man page created. - -> It should be installed in /usr/share/man, or a similar directory -> depending on how your perl is set up and how you did the install. -> --[[Joey]] - -> Found it, in /usr/local/share/man, since no other man pages are in either /usr/share/man or in /usr/local/share/man the ikiwiki -> man page is a bit lonely, and more to the point not on my MANPATH. Still I have found it now, I'll just move it to somewhere -> more sensible. [[Chris]] - -* Running "ikiwiki --setup ikiwiki.setup" doesn't do anything. I have edited ikiwiki.setup to -my local settings. There are no errors but neither does anything get compiled. An ikiwiki -command to explicitly do the compile works fine. Am I misunderstanding something here? - -> Further tests indicate that ikiwiki isn't seeing changed files so doesn't always rebuild. -> How does ikiwiki decide when to rebuild? I tried a full command line like "ikiwiki --verbose ikiwiki ~/public_html/ikiwiki --url=http://www.isbd.ltd.uk/~chris/ikiwiki/" and that doesn't do anything -either though it was the command line I originally used to compile. After a long interval I 'touch'ed -the files and then it *did* compile but 'touch'ing the files after a few minutes only doesn't seem to force a recompile. I'm even more confused! - -> ikiwiki only compiles files whose modification times have changed. It -> should see any change made as close as a second after the last compile. -> When run with --setup, ikiwiki always rebuilds every file in the wiki. If -> --setup is not working, you must have it pointed at the wrong path or -> something; you can pass -v to see what it's doing. I don't know why it -> would not see recently changed files; you could try stracing it. -> --[[Joey]] +[[toc ]] -> OK, thanks, I don't quite know what was happening before but it seems to be working right now. -> --[[Chris]] - ->> Weird. I wish I knew what happened, but as it's working now, I'm ->> guessing some kind of user error was involved. --[[Joey]] +# Installation/Setup questions -* I wish there was a mailing list, much easier for this sort of stuff than this, apart from -anything else I get to use a decent editor. +(I've moved HarleyPig's problem to its [[own_page|bugs/xgettext_issue]] +--[[Joey]]) ---- # Excellent - how do I translate a TWiki site? @@ -159,7 +117,7 @@ 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. +> 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 @@ -189,52 +147,6 @@ Ok, that's my last 2 cents for a while. --[Mazirian](http://mazirian.com) ---- -# 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 - ->>> 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. @@ -253,20 +165,26 @@ Clicking on an old "?" or going to a create link but new Markdown content exists ---- -# Refreshing RecentChanges page +# User database tools? -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 +Any tool to view user database? -> 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]] +Any tool to edit the user database? ->> 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 +> No, but it's fairly easy to write such tools in perl. For example, to +> list all users in the user database: ->>> Seems reasonable --[[Joey]] + joey@kodama:~/src/joeywiki/.ikiwiki>perl -le 'use Storable; my $userinfo=Storable::retrieve("userdb"); print $_ foreach keys %$userinfo' + http://joey.kitenet.net/ + foo + +> To list each user's email address: + + joey@kodama:~/src/joeywiki/.ikiwiki>perl -le 'use Storable; my $userinfo=Storable::retrieve("userdb"); print $userinfo->{$_}->{email} foreach keys %$userinfo' + + joey@kitenet.net + +> Editing is simply a matter of changing values and calling Storable::store(). +> I've not written actual utilities to do this yet because I've only needed +> to do it rarely, and the data I've wanted has been different each time. +> --[[Joey]]