aboutsummaryrefslogtreecommitdiff
path: root/doc/index
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-01-28 01:20:25 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-01-28 01:20:25 +0000
commitfa1cb20542a8c249706e0b219c70682e22af915a (patch)
tree7326e10f99044b5c7ae1c639c9b93b5168979f17 /doc/index
parent27797a26671a8c492babe699758d092ef33fdb75 (diff)
downloadikiwiki-fa1cb20542a8c249706e0b219c70682e22af915a.tar
ikiwiki-fa1cb20542a8c249706e0b219c70682e22af915a.tar.gz
split out into its own page
Diffstat (limited to 'doc/index')
-rw-r--r--doc/index/discussion.mdwn20
1 files changed, 0 insertions, 20 deletions
diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn
index 05b034026..904cedeb6 100644
--- a/doc/index/discussion.mdwn
+++ b/doc/index/discussion.mdwn
@@ -172,23 +172,3 @@ Clicking on an old "?" or going to a create link but new Markdown content exists
>>> 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
-
->>> Seems reasonable --[[Joey]]