response

[git.ikiwiki.info.git] / doc / index / discussion.mdwn

diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn
index 83f5d3c77976870cdcb4af332d71b15b9630328b..8e410d639f4ec1a826d78e6dfdef80a48e278cac 100644 (file)
--- a/doc/index/discussion.mdwn
+++ b/doc/index/discussion.mdwn
@@ -290,6 +290,11 @@ Clicking on an old "?" or going to a create link but new Markdown content exists
 >> 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
@@ -302,6 +307,12 @@ in WWW browser tab than subscribing to page. --Pawel
 > 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
+
 ----
 
 # Fall back for templatedir
@@ -314,3 +325,5 @@ As it is now, RecentChanges will have Perl CGI error and Preferences will be an
 I can quickly make a patch and submit to the patch queue. Any comments?
 
 > I'd probably accept a patch immediately. --[[Joey]]
+
+>> at [[patchqueue/fallback_for_templates]] --reed
\ No newline at end of file