summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-01-11 20:00:04 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-01-11 20:00:04 +0000
commitb1ccc0d2976ec93b81e232782fa8401612d23059 (patch)
treed879f1476dc8e426d71495d97bb0cc82808f7192
parent2c90067c83f22568c0451ece0ad524aa3377f13e (diff)
responses
-rw-r--r--doc/index/discussion.mdwn11
1 files changed, 10 insertions, 1 deletions
diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn
index 151a1a5cf..d409a30e2 100644
--- a/doc/index/discussion.mdwn
+++ b/doc/index/discussion.mdwn
@@ -284,6 +284,9 @@ or the path to the sub-page. I think this is handled by the htmllink() routine.
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
@@ -292,6 +295,10 @@ 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
@@ -301,4 +308,6 @@ 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? \ No newline at end of file
+I can quickly make a patch and submit to the patch queue. Any comments?
+
+> I'd probably accept a patch immediately. --[[Joey]]