Alternatively (and maybe more easily), are you in a position to retrieve 2.1.5 HEAD and test
your case there?
The cachekey that is used for aggregated content is composed of the individual key-parts of the aggregation, i just have the feeling that it does not get invalidated properly sometimes.
How do you calculate your cachekey in the log-on component?
Oscar Picasso wrote:
Hi,
I have installed the 2.1.4 version and realized I have the same problem.
Let's try to explain it.
We have:
+ aggregate - part A is generated by a cacheable component. The content depends on the uri. Example: > http://localhost/my-first-section ==> part A = "The content of my first section" > http://localhost/my-section-section ==> part A = "The content of my second section" - part B is generated by a cacheable component whose content depends only of whether the user is logged or not. The login status is part of the key of the cacheable component.
Part A and B, work fine when used separately whether or not caching is enabled. If caching is not enabled they work fine also in an aggregation.
But if A and B part of an aggregation and caching is enabled I run into the problems.
example of navigation sequence:
http://localhost/my-first-section + user not logged ==> first section + not logged content (OK)
http://localhost/my-second-section + user not logged ==> second section + not logged content (OK)
++ login
http://localhost/my-first-section + user is logged ==> first section + logged content (OK)
http://localhost/my-second-section + user is logged ==> second section + logged content (OK)
++ logout
http://localhost/my-second-section + user not logged
==> - second section (OK)
- logged content (**PROBLEM**)
(It should be 'not logged content').
Since my post I have found a workaround: I use a different uri whether the user is logged or not.
It seems the problem arise because the key use to cache the aggregated content doesn't use the individual keys of the parts (not quit sure I am correct here though). I have also to add that the problem was not reproductible in a systematic way.
--- Jorg Heymans <[EMAIL PROTECTED]> wrote:
Can you elaborate a bit more on what exactly you're experiencing (pipeline snippets etc)? There was a bug in 2.1.3 with nested aggregations and caching but it automagically disappeared in 2.1.5.
Oscar Picasso wrote:
Hi,
I am using the 2.1.5-dev version and am experiencing really weird things
when I
use aggregation with caching pipelines.
Has the caching mechanism changed between 2.1.5 and 2.1.4?
Thanks
__________________________________ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
__________________________________ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
