responses

master
joey 2007-01-11 20:00:04 +00:00
parent 2c90067c83
commit b1ccc0d297
1 changed files with 10 additions and 1 deletions

View File

@ -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. 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". 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 # 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 It can be useful for users like me which rather prefer watching the last changes
in WWW browser tab than subscribing to page. --Pawel 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 # Fall back for templatedir
@ -302,3 +309,5 @@ And then have it fall back to the location as configured at build time (like /us
This would be similar to _underlaydir_. I don't think any extra configuration directive is needed. 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. 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 can quickly make a patch and submit to the patch queue. Any comments?
> I'd probably accept a patch immediately. --[[Joey]]