responses and reorg
parent
8c0f961264
commit
bf4e6716cc
|
@ -21,14 +21,14 @@ something, that I think is very valuable.
|
||||||
|
|
||||||
----
|
----
|
||||||
|
|
||||||
Some questions about the RecentChanges function.
|
Some questions about the RecentChanges function. -- Ethan
|
||||||
|
|
||||||
* Why isn't it statically-genereated, but generated dynamically by CGI? It seems like it could be beneficial to have it rendered in the post-commit hook, just like everything else in the wiki.
|
> (Moved to [[todo/recentchanges]] --[[Joey]])
|
||||||
* Also, is it planned/desired that recent changes generate the same information in RSS feed format? This seems like it could be a useful way to keep track of the wiki as a whole.
|
|
||||||
* Lastly, would it be possible to use the recent changes code with a pagespec? I understand this sort of infringes on territory covered by the inline plugin, but the inline plugin only puts a page in the RSS feed once, when it's created, and I imagine some people -- some deranged, obsessive-compulsive people like myself -- would like to know about the changes made to existing pages as well as newly-created pages.
|
|
||||||
|
|
||||||
Thanks for your time. -- Ethan
|
|
||||||
|
|
||||||
----
|
----
|
||||||
|
|
||||||
Also, I'd like to request another template parameter which is just $config{url}. That way you won't have to hard-code the URL of the wiki into the template. -- Ethan
|
Also, I'd like to request another template parameter which is just
|
||||||
|
$config{url}. That way you won't have to hard-code the URL of the wiki into
|
||||||
|
the template. -- Ethan
|
||||||
|
|
||||||
|
> That's already available in the BASEURL parameter. --[[Joey]]
|
||||||
|
|
|
@ -0,0 +1,23 @@
|
||||||
|
* Why isn't it statically-genereated, but generated dynamically by CGI? It
|
||||||
|
seems like it could be beneficial to have it rendered in the post-commit
|
||||||
|
hook, just like everything else in the wiki.
|
||||||
|
|
||||||
|
I hope to statically generate it eventually, currently the problem is
|
||||||
|
that it takes at least several seconds to generate the recentchanges
|
||||||
|
page, and adding several seconds to every page edit is not desiriable. If
|
||||||
|
the time can be reduced it could be done, I'm also not adverse to
|
||||||
|
adding an optional way to statically render it even at the current speed.
|
||||||
|
|
||||||
|
* Also, is it planned/desired that recent changes generate the same
|
||||||
|
information in RSS feed format? This seems like it could be a useful way
|
||||||
|
to keep track of the wiki as a whole.
|
||||||
|
|
||||||
|
This is used by various interwiki type things, I think, so should be
|
||||||
|
done..
|
||||||
|
|
||||||
|
* Lastly, would it be possible to use the recent changes code with a
|
||||||
|
pagespec? I understand this sort of infringes on territory covered by the
|
||||||
|
inline plugin, but the inline plugin only puts a page in the RSS feed
|
||||||
|
once, when it's created, and I imagine some people -- some deranged,
|
||||||
|
obsessive-compulsive people like myself -- would like to know about the
|
||||||
|
changes made to existing pages as well as newly-created pages.
|
Loading…
Reference in New Issue