Avoid Clearing the Entire Site Cache When Saving a Resource

In classic Evolution CMS the default save flow is intentionally conservative: after a resource is updated, the system clears cache broadly to avoid serving stale trees, menus, and snippet output. That is why a single edit often appears to invalidate the whole site.

What is happening

Resource output in Evolution CMS is rarely isolated to one page. A saved document may affect Wayfinder menus, DocLister listings, sitemap output, breadcrumbs, caches built by plugins, and parent-child navigation. Global cache clearing is the safe default.

When this becomes a problem

• large sites with heavy snippet output
• catalog projects where editors save resources frequently
• projects with custom data imports or background updates

A practical approach

If you need narrower cache invalidation, treat it as custom project logic. Usually that means a plugin or service layer that clears only the fragments you own, while leaving the stock Evolution cache behavior alone unless you fully understand the side effects.

In practice the safer strategy is:

• leave core cache clearing intact for standard editing
• reduce expensive uncached snippets where possible
• move heavy derived data into dedicated caches you can rebuild selectively

Recommendation

Do not try to “optimize” cache clearing blindly. First measure what actually slows down saves, then decide whether you need lighter snippet usage, better cache design, or a custom invalidation plugin.