Unless all cache files are deleted somehow every time there is a change ?
Yes. This is exactly what I would like to have. Ideally, one could
define the cached page and group names (via regexpr) that are to be
deleted when an edit/new action is invoked on a particular page. That
way one
Hi,
Christophe David wrote:
I wonder how to define the dependencies adequately, as there are so
many things that can impact a page... In particular,
PageTextVariables changes seem to be extremely difficult to track
efficiently...
Yes. That's why deleting *all* cached pages after an
I just had a site vandalized via a new method I hadn't seen before, and
the hosting service was incredulous of.
The entire site's group ownership (this being a UNIX system) was changed
to igsvirt. Then all of the wiki.d files (which are group writable)
were overwritten with identical HTML
All,
I am re-phrasing my initial request to reduce confusion and hoping to
hear from someone who has done the following:
Changing the layout of Main.HomePage with a different skin from all
the other pages. My intention is to have Main.HomePage serve as an
editable entry page/portal to a series
Hi all,
My page still blank in edit mode.
my pmwiki version is 2.1.27
The Page Site.editForm is good so I uploaded again the wikilib.d folder but
It still doesn't work !
An idea ?
HHHeeellppp
--
cheers
___
D;)
Hi all,
My page still blank in edit mode.
my pmwiki version is 2.1.27
The Page Site.editForm is good so I uploaded again the wikilib.d folder but
It still doesn't work !
An idea ?
HHHeeellppp !
--
cheers
___
D;)
On Tue, Aug 14, 2007 at 08:55:01AM -0400, Ashwin wrote:
Changing the layout of Main.HomePage with a different skin from all
the other pages. My intention is to have Main.HomePage serve as an
editable entry page/portal to a series of other subsection of the
website.
Well, you can make
Tegan,Neil -- this is exactly what I was looking for thanks
Tegan Dowling [EMAIL PROTECTED] wrote: On 8/13/07, wiki question wrote:
We are setting up a wiki at work for an entire department. I am looking for
a standard set of procedures to publish outlining the basic rules of
engagement
Hello,
I modified the ticket a bit. Detecting dependencies automatically is a
bit too much for a static caching, so I think it is enough if users can
define dependencies in the (:static :) parameter.
So it generally works like this: Get-requests are cached. If a user
modifies a page with a
On Tue, Aug 14, 2007 at 10:04:51PM +0200, Thomas Bley wrote:
http://pmwiki.org/wiki/PITS/00966
Quick response:
Having looked at the code in PITS.00966 -- I don't see how it's
substantially different from PmWiki's built-in HTML caching.
In particular, the code in PITS.00966 says:
On Tue, Aug 14, 2007 at 04:31:41PM +0800, Martin Spindler wrote:
Christophe David wrote:
I wonder how to define the dependencies adequately, as there are so
many things that can impact a page... In particular,
PageTextVariables changes seem to be extremely difficult to track
Hello,
$EnableHTMLCache is 1 and it is being used (I removed some NoCache()
calls for this), but it is a pmwiki-2.1.10, so maybe newer versions are
faster.
The page tested has no (:include :) or other special things.
Differences in the code:
The pageCacheFile is written with:
fwrite($fp,
Hi,
Patrick R. Michaud wrote:
...but in the code given by PITS.00966, the value being written
to the cache file is the result of MarkupToHTML(), yes?
That would seem to imply that none of the skin, sidebar, pageaction,
or other items are being saved in the cached .html file, and
displaying
I am writing some PHP rules (scripts) files.
In one, I have some javascript that should exist only once per page in
addition to another tag. How do I detect that the user has use (:tag
blah:) more than once so I can omit emitting the singleton content?
I am trying
SDV('$Flag']), 0);
Thanks Dave, I would like to hide all rows but the top one, so the users can
click/toggle something to drop down the whole table. I will use this for
tables that are rather long and will be in the middle of otherwise longish
pages of information. I want the users to be able to scan the page and
Patrick R. Michaud wrote:
This is effectively what PmWiki's built-in caching mechanism does --
any change to any page invalidates the cached versions of the
pages. (It doesn't delete them... but then it doesn't need to.)
But PmWiki isn't bypassed in the built-in caching, is it? I think the
On Wed, Aug 15, 2007 at 09:49:14AM +0800, Martin Spindler wrote:
Patrick R. Michaud wrote:
This is effectively what PmWiki's built-in caching mechanism does --
any change to any page invalidates the cached versions of the
pages. (It doesn't delete them... but then it doesn't need to.)
On Wed, Aug 15, 2007 at 10:40:04AM +0800, Martin Spindler wrote:
Patrick R. Michaud wrote:
I'm thinking I may extend $EnableHTML to also cache the
complete HTML output so that it can be grabbed via a
rewrite rule, but try to do it a bit smartly with respect
to other items (e.g.,
18 matches
Mail list logo