.
You have. You can have getCache cache the output of any Element in MODx (Chunk, Snippet, Template Variable) for a certain amount of time, complementing the partial-page cache which can remain while only the Element you have called with getCache gets updated periodically.
If i got it right, it’s great.
it means that now we can set when the Cache Expires on every element we use on modx, in different from the Cache available now.
have i understood it correctly?
There is a simple example using the getResources snippet here, and I will add more today.
if it’s possible to have an explanation of usage (an example/scenario) of how (get)cache works, it would be awesome.
thanks
[[!getResourcesTag? &elementClass=`modSnippet` &element=`getResources` &tpl=`blogPost` &parents=`34,35` &limit=`5` &includeContent=`1` &includeTVs=`1` &showHidden=`0` &hideContainers=`1` &cache=`0` &pageVarKey=`page` ]]

Sure, I suppose you could, though I don’t see any reason to ever have Wayfinder uncached (unless you are showing personalized menus, then you never want it cached). If you edit a Resource, the cache is refreshed, so all your Wayfinder calls are in turn refreshed.
can i use getCache with Wayfinder?
Quote from: Kristalin at Aug 04, 2011, 04:28 PMSure, I suppose you could, though I don’t see any reason to ever have Wayfinder uncached (unless you are showing personalized menus, then you never want it cached). If you edit a Resource, the cache is refreshed, so all your Wayfinder calls are in turn refreshed.
can i use getCache with Wayfinder?