To create a set of list items consisting solely of $:MyPageTextVariable:
foreach($matches as $m) {
$ptv = PVSE(PageVar($m, '$:MyPageTextVariable'));
$out .= li$ptv/li\n;
}
This works great and much faster than templates. It is indeed the
right way to produce large complex
This will create a list of the values of $:MyPageTextVariable
It looks that using a custom function instead of a pagelist template
has a side effect on the count= parameter, which does not appear to be
processed correctly.
fmt=#MyFormat (defined in LocalTemplates) : count= works OK
On Mon, Jun 11, 2007 at 02:46:37PM +0200, Christophe David wrote:
This will create a list of the values of $:MyPageTextVariable
It looks that using a custom function instead of a pagelist template
has a side effect on the count= parameter, which does not appear to be
processed correctly.
How does it work with the PHP cache engine?
1. Are all pages cached by eaccelerator regardless of whether they
are are cached by PmWiki?
2. What happens to the dynamic pages? Pagelist, MetaTags...
3. Do we have double caching? Cached by HTMLcache eaccelerator?
Any penalty for that?
...
These
For really fast processing and output of pagelists, one should
really create a custom formatting function for pagelist and not
rely solely on the markup rendering engine. Prior to pagelist
templates, this is how we did all of our output stuff.
I am afraid I missed something here. Do you
On Sun, Jun 10, 2007 at 08:17:13AM +0200, Christophe David wrote:
For really fast processing and output of pagelists, one should
really create a custom formatting function for pagelist and not
rely solely on the markup rendering engine. Prior to pagelist
templates, this is how we did all of
Essentially, a custom formatting function will generally look like:
Hope this helps -- let me know if you need any further hints.
Thanks a lot. I just copied your example and it works great.
Could you please show me how to convert the following parts of a
pagelist template
On Sun, Jun 10, 2007 at 09:15:39PM +0200, Christophe David wrote:
Essentially, a custom formatting function will generally look like:
Hope this helps -- let me know if you need any further hints.
Thanks a lot. I just copied your example and it works great.
Could you please show me how to
This does require a fair bit of additional code and complexity to
implement, and it also means reworking some of PmWiki's existing
something cached is out of date structures. And overall it hasn't
been a high priority, but I might be able to squeeze some time in
to improve it.
The root
On Sat, Jun 09, 2007 at 05:29:05PM +0200, Christophe David wrote:
I'm a little reluctant to do a workaround like this, at least in the core
I don't have a really good answer at the moment.
Just an idea: if I understand correctly, the target attribute (target=
in a wiki page file) contains a
On Sat, Jun 09, 2007 at 06:41:54PM +0200, Christophe David wrote:
This does require a fair bit of additional code and complexity to
implement, and it also means reworking some of PmWiki's existing
something cached is out of date structures. And overall it hasn't
been a high priority, but I
When generating long pagelists with custom templates, PmWiki sometimes
appears to exceed system resources and ends up returning a blank
screen.
$PageCacheDir = 'cache.d';
$PageListCacheDir= 'cache.d';
$EnableHTMLCache = 1;
$EnableIMSCaching = 1;
help a lot, as the resulting page is
On Fri, Jun 08, 2007 at 11:19:43AM +0200, Christophe David wrote:
$PageCacheDir = 'cache.d';
$PageListCacheDir= 'cache.d';
$EnableHTMLCache = 1;
$EnableIMSCaching = 1;
help a lot, as the resulting page is cached, and the next requests
only need to read the cached version.
13 matches
Mail list logo
