Hello,
There is a very strange behaviour that my site exibits
ever since I've upgraded my 2.1 dev code from what it
was in Nov-Dec last year to the most current version
(less than a week old).
Here is what's going on. There is a portlet which is
generated by calling another pipeline fragment
into the
Cocoon's/Avalon/Excalibur source code and debug.
-Original Message-
From: Alex Romayev [mailto:[EMAIL PROTECTED]
Sent: 03 March 2003 02:57PM
To: [EMAIL PROTECTED]
Subject: Very strange behaviour -- caching bug?
Hello,
There is a very strange behaviour that my site exibits
ever since
and debug.
-Original Message-
From: Alex Romayev [mailto:[EMAIL PROTECTED]
Sent: 03 March 2003 02:57PM
To: [EMAIL PROTECTED]
Subject: Very strange behaviour -- caching bug?
Hello,
There is a very strange behaviour that my site
exibits
ever since I've upgraded my 2.1 dev code
To: [EMAIL PROTECTED]
Subject: RE: Very strange behaviour -- caching bug?
Hi Mark,
Thanks for your help. I like your test case -- it
simpler and cleaner. Do you (or anyone else) know how
to submit this as a bug to make sure the developers
know about it?
Cheers,
-Alex
--- Mark H [EMAIL
On pon, mar 03, 2003 at 10:01:03 -0800, Alex Romayev wrote:
Hi Mark,
Thanks for your help. I like your test case -- it
simpler and cleaner. Do you (or anyone else) know how
to submit this as a bug to make sure the developers
know about it?
I have encountered the same bug (I think) or
Do you know the syntax for making a pipeline
noncaching?
--- Leszek Gawron [EMAIL PROTECTED] wrote:
On pon, mar 03, 2003 at 10:01:03 -0800, Alex Romayev
wrote:
Hi Mark,
Thanks for your help. I like your test case -- it
simpler and cleaner. Do you (or anyone else) know
how
to
On pon, mar 03, 2003 at 11:27:10 -0800, Alex Romayev wrote:
Do you know the syntax for making a pipeline
noncaching?
first see if your main sitemap.xmap contains different pipeline implementation
(grep for caching, noncaching)
use it like this:
map:pipeline type=noncaching
!-- map:match
