You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a site that I recently updated from an old 2.2.x version to 2.5.1, the problem I face now is that chunks called via getCache do not work as expected anymore. By that I mean that an uncached snippet call again to getCache (or other uncached elements, doesn't matter) at the deepest level is processed and "hardcoded" into the output/result instead of staying in the cached output as a modx tag.
The structure is roughly as follows: Template with [[!getCache? <calling a chunk>]] > inside that chunk there are other cached chunks in a wrapper structure, e.g. <div>[[$somechunk]]</div><div>[[$anotherchunk]]</div> inside [[$somechunk]] there is another call [[!getCache? <calling a snippet>]], that last call was there as a modx tag in 2.2.x, I have proof of that, can send the exact cachefiles for both 2.2.x and 2.5.x. but in 2.5.x this tag is no longer there but it's the html output from that snippet call which is therefore cached in the main output of the initial getCache snippet call...resulting in stale HTML instead of fresh one (on each request).
any idea if this is something with getCache or a problem with the parser or the structure?
I use getCache in this instance because I can specify a specific cache partition to cache that chunk in and allow custom clearing of that cache partition via manager.
The text was updated successfully, but these errors were encountered:
I have a site that I recently updated from an old 2.2.x version to 2.5.1, the problem I face now is that chunks called via getCache do not work as expected anymore. By that I mean that an uncached snippet call again to getCache (or other uncached elements, doesn't matter) at the deepest level is processed and "hardcoded" into the output/result instead of staying in the cached output as a modx tag.
The structure is roughly as follows: Template with
[[!getCache? <calling a chunk>]]
> inside that chunk there are other cached chunks in a wrapper structure, e.g.<div>[[$somechunk]]</div><div>[[$anotherchunk]]</div>
inside[[$somechunk]]
there is another call[[!getCache? <calling a snippet>]]
, that last call was there as a modx tag in 2.2.x, I have proof of that, can send the exact cachefiles for both 2.2.x and 2.5.x. but in 2.5.x this tag is no longer there but it's the html output from that snippet call which is therefore cached in the main output of the initial getCache snippet call...resulting in stale HTML instead of fresh one (on each request).I have no clue where that is coming from, maybe yoleg/revolution@eaa4ff7#diff-351a00a3f45f439700971494783acde4 ? I tried that systemsetting
parser_recurse_uncacheable
setting it from Yes to No and back, but no change...any idea if this is something with getCache or a problem with the parser or the structure?
I use getCache in this instance because I can specify a specific cache partition to cache that chunk in and allow custom clearing of that cache partition via manager.
The text was updated successfully, but these errors were encountered: