Caching Nested Snippet Output More Aggressively in Evolution CMS

Legacy MODX Evolution documentation often taught one safe rule: if a snippet contains another snippet call, make the outer call uncached. That is correct for dynamic filters and request-driven widgets, but it is not always the most efficient choice for static output.

The point of the note

If the outer snippet output is effectively static, you can often keep the whole chain cached instead of forcing the parser to rebuild it every time.

[[Ditto? &tpl=`tpl-tpl`]]

// inside tpl-tpl
[[snippet]]

When this is safe

• the content does not depend on current request parameters
• there is no per-user personalization
• the nested snippet output is also effectively static

When not to do it

• filters, sorting, pagination, or search depend on the request
• the listing must react to session or user state
• the manager needs changes to appear immediately without cache refresh

This is a small optimization, but on older sites it often made section pages cheaper to render simply by letting more of the parser result fall into cache.